Lan Barnes wrote:
Well said. (OK, really a buckboard with a lawnmower engine.) Also, thanks for (I guess?) defending my zeal. Really, the pain factor of switching to svn is like a couple of hours work for most home hobbyists. I *highly* recommend giving svn a try. Or Perforce, if free-as-in-beer doesn't cause a skin rash in you.
Personally, having used both RCS and CVS (in fact, I still *have* to use both for some projects), I like and prefer Perforce. I currently use the free version of Perforce here at work for all my software projects as well as any documentation. My first exposure to it was while at Akamai where we used it for version control of just about everything we needed version control for.
It has a lot of features I like, nice GUIs for both Windows and Linux (and a web front-end as well), and a good commend line interface. I especially like the ability to tie a set of changes to a reported bug I need to fix or a feature I want to implement.
Yes, there's lots of different free and commercial version control systems out there, but so far I've found Perforce to meet my needs, and I don't mind paying for something that works well and runs on the OS I want to use it on (I haven't had the need to pay for Perforce yet, but I am trying to get it implemented for more departments here - replacing RCS - which will mean actually paying for licenses).
PGA -- Paul G. Allen Owner, Sr. Engineer, BSIT/SE Random Logic Consulting Services www.randomlogic.com -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
