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
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
That's an interesting observation. (Score:1)
The thing is though, that I have no fear of branching because there's a "recipe" for merging and I don't have to think too much about it other than to record revision numbers in the log. So I'm all for branching in subversion. Also though, I tend to not do any complica
Re: (Score:2)
The thing is though, that I have no fear of branching because there's a "recipe" for merging and I don't have to think too much about it other than to record revision numbers in the log.
Bingo; I think you just identified a huge chunk of my fear: I barely had merging in CVS down, and I don't yet fully understand the "recipe" for it in Subversion. So, schwern (or anybody), should I spend time getting really comfortable with merging in subversion and then move to SVK, or will SVK make all of that into time wasted?
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:That's an interesting observation. (Score:2)
After that I'd say jump directly to SVK or just use svnmerge.
Reply to This
Parent
Re: (Score:2)
Thanks for the advice! :)
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers