Table of Contents
If you are already familiar with cvsnt and are just trying to learn a particular feature or remember a certain command, you can probably skip everything here.
For example, bugs sometimes creep in when software is modified, and you might not detect the bug until a long time after you make the modification. With cvsnt, you can easily retrieve old versions to see exactly which change caused the bug. This can sometimes be a big help.
You could of course save every version of every file you have ever created. This would however waste an enormous amount of disk space. cvsnt stores all the versions of a file in a single file in a clever way that only stores the differences between versions.
cvsnt also helps you if you are part of a group of people working on the same project. It is all too easy to overwrite each others' changes unless you are extremely careful. Some editors, like gnu Emacs, try to make sure that the same file is never modified by two people at the same time. Unfortunately, if someone is using another editor, that safeguard will not work. cvsnt solves this problem by insulating the different developers from each other. Every developer works in his own directory, and cvsnt merges the work when each developer is done.
cvsnt started out as a bunch of shell scripts written by Dick Grune, posted to the newsgroup comp.sources.unix in the volume 6 release of December, 1986. While no actual code from these shell scripts is present in the current version of cvsnt much of the cvsnt conflict resolution algorithms come from them.
In April, 1989, Brian Berliner designed and coded cvs. Jeff Polk later helped Brian with the design of the cvs module and vendor branch support.
In December, 1999 Tony Hoyle converted the unix based CVS to run under Windows Server (Windows NT). This later became cvsnt, which developed into a project of its own.
CVSNT is now a major project with solid commercial backing, and an active support community.
For support please contact firstname.lastname@example.org. The mailing list is no longer used for support, but the history is maintained online as well as the current bug database: