There's a scalability issue with cvs2svn.py in its use of ?dbm for local
temporary storage while it's doing the conversion to produce the dump
file. That issue is being worked on now. You may want to hold tight,
or even better, volunteer to test fixes :-)
Cheers...
Bruce
Corris Randall wrote:
> Hello all,
>
> I'd love to switch my developers to svn, they're eager
> too. however, there are two things that are currently
> stopping us. 1. the conversion time is way too long.
> I've gove a 3 GB repo that's taking days to run. and
> 2. the svn externals support isn't quite the same as
> the cvs modules. I can live without 1. ( maybe I
> can convince them to start from scratch. ) but I can't
> live without 2. our cvs modules file is _huge_, and
> we have tons of dependancies on common code, internal
> and external libraries.
>
> This wouldn't really be a problem, except that we tag
> and branch on the cvs modules by name, and from what
> I've read, the externals property won't exactly work
> when moving things around in the branches & tags dirs.
>
>
> Will there be something similar to the cvs modules
> file that will work well with branching/tagging &
> including common code?
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Search - Find what you’re looking for faster
> http://search.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 10 19:43:09 2004