CVS Information Pages

• Server and repository administration
• Usage tips
• History
• Developer notebooks, feature requests, and patches

Server and repository administration

• Controlling Access for Various Users discusses the available ways of controlling user access to repositories and links to a patch to add fine-grained access control.
• Converting to CVS from Another Version Control System discusses two ways of keeping version history when you move from another version control system to CVS.
• Multisite discusses ways of maintaining multiple CVS repositories for developers working together on the same projects but on different sites. 
• System Requirements discusses memory and CPU usage for both the CVS client and the CVS server.
• Triggers and Logging in CVS points to tools and documents you can use to enhance CVS's logs.

Return to topic list

Usage tips

• Keeping a Checked Out Copy mentions a couple of ways to keep an up-to-date copy of a repository's files, without creating a working directory (with the CVS subdirectories).
• System Administration points to documents discussing the use of CVS in system administration.
• Tracking Changes lists several approaches to using CVS in an overall change management system.
• CVS and the Web points to tools and documentation for using CVS to maintain a Web site.

Return to topic list

History

• "Halibut" Release tells the story of the release of CVS 1.10.

Return to topic list

Developer notebooks, feature requests, and patches

• Branching, Merging, Remove/Add includes a wishlist of features enhancing CVS's support for branches and for merging branches. 
• Change Control discusses how you could use CVS to track feature requests and bug reports in separate systems.
• CVS Interface to RCS Library is developer-level notes on replacing the current RCS-based repository format.
• DAV (Distributed Authoring and Versioning) is a discussion of how the DAV protocol might be used in place of the existing CVS client-server protocol.
• W3C Document Object Model (DOM) demonstrates how a patch to CVS generates tagged log output, which can be converted to XML and HTML for manipulation via scripting languages in a Web browser.
• Keeping a Checked Out Copy discusses several ways of getting a list of files in a CVS repository.
• CVS for Macintosh discusses issues related to the MacOS way of handling files (e.g., end-of-line character and forks).
• Separating Metadata in CVS discusses how future versions of CVS could store metadata (data about the repository's contents) apart from the RCS files that make up the repository itself.
• Networking and Security discusses CVS networking (for example, running the CVS pserver on ports other than 2401 and how to use SOCKS for the CVS client) and security (like encryption and password authentication).
• Networking points out different reasons why you'd want to run CVS in its client-server mode versus using a networked file system.
• CVS Output points to available patches to enhance the output of CVS logs and reports.
• Resource Consumption discusses CVS memory and CPU usage and ways they could be optimized.
• Reserved Checkouts includes tips on using locking-style reserved checkouts (versus the CVS default of update/merge/commit) and patches to make the CVS edit command more strict (to better emulate reserved checkouts).
• Set Up lists patches and bug reports relating to installing and configuring CVS. 
• Specifying Files includes patches and bug reports relating to CVS file handling.
• Triggers and Logging in CVS discusses how CVS can be enhanced by adding triggers -- plug-ins that get triggered by certain actions.
• CVS and the Web points to mod_cvs and DAV for working with CVS and Web servers.
• Wrappers (-t/-f) discusses "wrappers" support available for older versions of CVS, to support treating a directory as if it were a file.

Return to topic list