Re: cvs2svn patch in the works...

> object? If so, then you could just as well do:
>
> def get_key(f, r):
> return intern(f + '--' + r)
>
> which works all the way back to Python 1.5.
>
> However, both approaches will not scale properly. It seems that you'll be
> creating keys for practically every file *and* revision that is found in the
> conversion process. That isn't going to work :-)

Maybe if we create a BDB database of all the revisions and files.
Oh, wait.
:)

I repeat that anyone doing serious work on cvs2svn, should grab copies
(through rsync) of the gdb and gcc CVS repos.

gcc is a large repository with tons of branches (and branches created on
branches), etc, tons of revisions, and tons of files.
It should convert in a reasonable amount of time, unless your algorithms
don't scale.
(IE if you've got an O(n^2) algorithm somewhere, it'll likely take days to
convert).

You'll also blow out your disk if you are creating too many copies or
something.
:)
--Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 24 06:06:18 2002