That's nice. Unless you, say, you want to: * Track renames of files. * Track changes to the repository as a whole, instead of per file. I care most about step

That's nice. Unless you, say, you want to: * Track renames of files. * Track changes to the repository as a whole, instead of per file. I care most about stepping through revisions of a project; inspection of the history of a particular file is a secondary concern for me, but is all that CVS can do. A "project" for me is usually a set of files that are interdependent to greater and lesser degrees. The best you get with CVS for tracking the versions of all the files in a repository is manually creating tags all the time. With Git, Subversion, Mercurial, Bazaar, etc you get this for free; it's how these tools work. (As an aside, DOS is also a proven operating system. For varying values of "proven".)