CVS Information

• Still asking what version control is and why you should use it? One nice introduction is the book Practical Software Configuration Management which discusses storing your software in version control and handling basic situations like coordinating edits by several people. It uses RCS in the examples, but many of the concepts would apply to CVS or other version control systems as well.
• The short CVS overview and the longer CVS datasheet list CVS features.
• System Requirements (memory, disk, &c)
• CVS and the Year 2000
• CVS Security
• CVS and the World Wide Web
• Particular issues:
  • Concerned about whether to use the non-client/server CVS with a networked file system, or whether to use the client/server CVS?
  • Concerned about CVS's use of unreserved checkouts (parallel development) rather than reserved checkouts (RCS/SCCS style locking)?
  • Wondering how to handle developers at multiple locations or organizations?
  • Trying to keep track of all the different changes that developers are checking into CVS?
  • Wanting to control the level of access that different people have to CVS?
  • Planning to convert from another version control system to CVS?
• Known Bugs in CVS.

Information at Other Sites

• Sean Dreilinger's site includes CVS documentation, a search engine which is specific to CVS sites, and more.
• Pascal Molli's site includes a list of software related to CVS, and more.
• The "How can I do revision control?" page is a very nice introduction to why you may want to use version control at all (particularly aimed at programmers). The rest of the site looks nice too (those parts which are completed).