It's been working pretty well for a while, though there are still some edge
cases. Anyway, if hg convert works well for you, not much need to switch!

> Dirkjan Ochtman <dirkjan@ochtman.nl> added the comment:
>
> You may want to try with hgsubversion.

I'll give it a try at some point, though I don't have an idea how
stable/usable it is right now.

Thanks.
        Rainer

> Patrick Mézard <pmezard@gmail.com> added the comment:
>
> Tags conversion may be really slow. It can be disabled with something like:
>
> --config convert.svn.tags=

Excellent tip: that brought the conversion time down from 12+ hours to 7
minutes :-)  Perhaps a corresponding warning could be added to hg
convert -h output?

Thanks.
        Rainer

Tags conversion may be really slow. It can be disabled with something like:

--config convert.svn.tags=

You may want to try with hgsubversion.

I'm currently using hg 1.4.1 with python 2.6.4 and subversion 1.6.6 to
regularly convert a local copy of the GCC svn repository (available via
rsync, cf. http://gcc.gnu.org/rsync.html) to a hg repository.  This is
running on a Sun Fire V880 with 6 1050 MHz CPUs, 12 GB RAM and local disks.
While the initial conversion took several days and a couple of restarts
(VM exhausted; I've been using 32-bit binaries), it finally completed.
I'm currently running regular incremental conversions after updating the
local copy of the svn repository.  Unfortunately, they are extremely slow:
although only about 30-60 revisions are added per day, the conversion takes
on the order of 12 to 13 hours.  I'm simply running

$ hg convert svn/repo hg/repo

I can hardly believe that this must be this slow.