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
help them think they understand.
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Use git; you won't have to deal with this. (Score:1)
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.
Reply to This
Re: (Score:2)
Thanks. I'll definitely look more into it.
I came into work this morning to discover our CVS server has a kernel panic; one of the only two guys who can fix it didn't arrive till just now, so at the moment I can't really use much of anything. :) Actually I can continue to commit to my SVK repository; just can't get all the updates that happened after I went home on Friday and over the weekend.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re: (Score:2)
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!
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers