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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • There are at least three functional ways to get from CVS to git listed on the Interfaces, Front-ends And Tools page on the git wiki [git.or.cz].

    If you want to be able to commit back to cvs, you probably want to go the git-cvsimport / git-cvsexportcommit route.

    • Thanks again. A little bit of reading, study, and practice, and now I see that git does in fact handle my gripe above quite nicely. Score 1 for git, 0 for svk, which disappoints me, because to be honest I'm biased in favor of svk. :)

      I love that with git I can take a long time specifically marking what I actually want to commit and that when I commit, unless I make an unconscious habit of using the -a option, I'll just commit the things I marked rather than possibly screwing up and committing everything! Score 1 for git over cvs, svn, and svk. Wow.

      I think git is going to end up being my final destination.

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers