All the Perl that's Practical to Extract and Report
use Perl Log In
jdavidb (1361)
(email not shown publicly)
http://voiceofjohn.blogspot.com/
J. David Blackstone has a Bachelor of Science in Computer Science and Engineering and nine years of experience at a wireless telecommunications company, where he learned Perl and never looked back. J. David has an advantage in that he works really hard, he has a passion for writing good software, and he knows many of the world's best Perl programmers.
SVK (and CVS)
I'm going to start using SVK for work, but I'll continue to be interfacing with our main repository which is CVS. Any tips and tricks people can offer me for making the two work together would be appreciated. If I understand correctly, SVK can't currently just talk to CVS as its backend like it does to Subversion, so I'll basically have to manually commit to CVS, and when I do that people won't see the intermediate changes I've made to my own local SVK depot. That's probably desirable behavior at this point, although I'd rather SVK manage talking to CVS for me.
If someone can persuade me that Git or something else talks to CVS and would be better for me, please do so. In terms of experience I feel pretty competent with CVS, moderately competent with Subversion (though I've never been comfortable with the way tags and branches were flattened into the filesystem namespace, and I never really learned how to weave around between branches; I figure I'll just skip learning that and depend on SVK to do it for me under the hood), and I have a week of experience with SVK. I watched part of Torvalds' rant where he described git and understood what I saw, for the most part.
--Donald E. Knuth
git and (other) (Score:1)
git-cvs is probably worth at least giving a try, and for use as a better frontend to your existing VCS, git's interface isn't very daunting.
We were both using svk a few years ago and got turned off of it after one too many "oops, I re-committed 50 random revisions" prob