Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

The Return of CVS! 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I can recommend cvs2svn [tigris.org]. It did a pretty reasonable job of converting my cvs repository to subversion. Of course, you'll want to go in afterwards and do a bit of tidying up, but on the whole it's pretty easy.

    The main problem is the time. It was pretty quick for my home repository, but the one at work took several hours and resulted in over 35,000 commits.

    -Dom

    • Yes, I used cvs2svn to do my initial conversion of a handful of projects but didn't do them all at once as I wasn't sure I was going to stick with SVN at the time. Kicking myself now for not having just done it all in one shot.

      I also recently did a conversion of a 500 meg (compressed) CVS work repo spanning about half a decade of development. Took just 2 hours to dump resulting in an 800 meg dump file and about an hour to load. 27,000 revisions. It did an excellent job of finding all the branches and tags and even dealt with all the hacking and shifting around of RCS files they've done over the years.

      And then the joys of being able to rename and delete directories begin.
      • Yes, the cleaning up after conversion import is the hard bit IMHO. I still haven't really found a good solution to reorganising a subversion repository. I'm still using a whole bunch of command line renames. Alas, I don't think there's a better way.

        -Dom

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.