The biggest thing CVS has going for it over MKS SI
is the (mostly) automatic merging of branches on
a project- or module-wide basis using 3-way diffs.
MKS merging is file-by-file, and is 2-way diff based
manual process, (or was, last time I checked, which was
a year ago or so).
A couple other points in CVS favor:
CVS is pretty portable, which can be important if
you're doing development on some obscure or very new
platform or OS. For example, I was able to run CVS on pre-beta
versions of SCO Unixware 7 before SCO had even picked
unixware 7 as the name. And now I am able to run it on
IBM's AIX5L on Itanium.
Also, MKS SI uses a locking scheme, like RCS, which,
if you've gotten used to CVS, this can be an annoyance to have
to constantly be locking things.
__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/
