Re: git-cvsimport doesn't quite work, wrt branches
- From
- sf <sf@b-i-t.de>
- Date
- Jun 14, 2006, 09:37 UTC
- Message-ID
- <448FD8E4.9040208@b-i-t.de>
- In-Reply-To
- <46a038f90606131555m7b1fa744g9770140c87598b7b@mail.gmail.com>
Martin Langhoff wrote: ...
> Yes, cvsps is relying on the wrong things. I am looking at parsecvs > and the cvs2svn tool and wondering where to from here.
...
> I am starting to look at what I can do with cvs2svn to get the import > into git. It seems to get very good patchsets, and it yields an easily > readable DB. I'll either learn Python, or read the DB from Perl > (probably from git-cvsimport).
SVN has a portable format called "dumpfile" (see http://svn.collab.net/repos/svn/trunk/notes/fs_dumprestore.txt) which is produced by "svnadmin dump ..." and "cvs2svn --dump-only ...".
Why not use it as input for importing into git?
Pros: - "svnadmin dump" should be fast - svn repositories can be tracked with "svnadmin dump" (just remember the last imported revision and restart from there) - cvs2svn seems to be very good at its job - only one tool needed
Cons: - Both svnadmin and cvs2svn only work on local repositories - cvs2svn cannot be used for tracking
Regards Stephan