User Reviews
Really getting old
by rds
CVS is good thanks to its popularity and frequent integration in most tools (IDE, software factories, well just about everywhere).
However, it's old, does not handle change sets and does not version directories. The only SCM I know which has less features I know is PVCS.
If you use CVS, it is really time to move to subversioN.
4 of 6 users found the following review helpful. Was this review helpful to you? Yes | No
Just good enough
by TheAlienist
CVS is the grand-daddy of source versioning systems and it shows. It's got all of the charm and reliability of a '88 ford taurus. It aint pretty, but by gosh it's everywhere!
What's there to like? It mostly works. Some projects have 10+ years of history using it. However, it has some pretty basic problems too. Tagging and branching is not only hard, it's slow and cumbersome.
Even with the massive adoption it's had, it's
4 of 8 users found the following review helpful. Was this review helpful to you? Yes | No
CVS vs. Subversion
CVS is very stable. In case of an hardware failure it does not destroy the repository like Subversion does. The worst case is some stale lock files lying around, which are automatically deleted on reboot by most Linux distributions.
CVS does support unique IDs for commits spanning multiple directories.
Popular CVS clients like Eclipse do support change sets.
CVS has very handy short version numbers on a per file basis.
0 of 1 users found the following review helpful. Was this review helpful to you? Yes | No
