CVS--Concurrent Versions System

This document is distributed under the GNU General Public License.
Please review before re-distributing this document.

Content Index

• Overview
  • What is CVS?
  • What is CVS not?
  • A sample session
    • Getting the source
    • Committing your changes
    • Cleaning up
    • Viewing differences
• The Repository
  • Telling CVS where your repository is
  • How data is stored in the repository
    • Where files are stored within the repository
    • File permissions
    • File Permission issues specific to Windows
    • The attic
    • The CVS directory in the repository
    • CVS locks in the repository
    • How files are stored in the CVSROOT directory
  • How data is stored in the working directory
  • The administrative files
    • Editing administrative files
  • Multiple repositories
  • Creating a repository
  • Backing up a repository
  • Moving a repository
  • Remote repositories
    • Server requirements
    • Connecting with rsh
    • Direct connection with password authentication
      • Setting up the server for password authentication
      • Using the client with password authentication
      • Security considerations with password authentication
    • Direct connection with GSSAPI
    • Direct connection with kerberos
    • Connecting with fork
  • Read-only repository access
  • Temporary directories for the server
• Starting a project with CVS
  • Setting up the files
    • Creating a directory tree from a number of files
    • Creating Files From Other Version Control Systems
    • Creating a directory tree from scratch
  • Defining the module
• Revisions
  • Revision numbers
  • Versions, revisions and releases
  • Assigning revisions
  • Tags--Symbolic revisions
  • Specifying what to tag from the working directory
  • Specifying what to tag by date or revision
  • Deleting, moving, and renaming tags
  • Tagging and adding and removing files
  • Sticky tags
• Branching and merging
  • What branches are good for
  • Creating a branch
  • Accessing branches
  • Branches and revisions
  • Magic branch numbers
  • Merging an entire branch
  • Merging from a branch several times
  • Merging differences between any two revisions
  • Merging can add or remove files
  • Merging and keywords
• Recursive behavior
• Adding, removing, and renaming files and directories
  • Adding files to a directory
  • Removing files
  • Removing directories
  • Moving and renaming files
    • The Normal way to Rename
    • Moving the history file
    • Copying the history file
  • Moving and renaming directories
• History browsing
  • Log messages
  • The history database
  • User-defined logging
  • Annotate command
• Handling binary files
  • The issues with binary files
  • How to store binary files
• Multiple developers
  • File status
  • Bringing a file up to date
  • Conflicts example
  • Informing others about commits
  • Several developers simultaneously attempting to run CVS
  • Mechanisms to track who is editing files
    • Telling CVS to watch certain files
    • Telling CVS to notify you
    • How to edit a file which is being watched
    • Information about who is watching and editing
    • Using watches with old versions of CVS
  • Choosing between reserved or unreserved checkouts
• Revision management
  • When to commit?
• Keyword substitution
  • Keyword List
  • Using keywords
  • Avoiding substitution
  • Substitution modes
  • Problems with the $@asis{}Log$ keyword.
• Tracking third-party sources
  • Importing for the first time
  • Updating with the import command
  • Reverting to the latest vendor release
  • How to handle binary files with cvs import
  • How to handle keyword substitution with cvs import
  • Multiple vendor branches
• How your build system interacts with CVS
• Special Files
• Guide to CVS commands
  • Overall structure of CVS commands
  • CVS's exit status
  • Default options and the ~/.cvsrc file
  • Global options
  • Common command options
  • admin--Administration
    • admin options
  • checkout--Check out sources for editing
    • checkout options
    • checkout examples
  • commit--Check files into the repository
    • commit options
    • commit examples
      • Committing to a branch
      • Creating the branch after editing
  • diff--Show differences between revisions
    • diff options
    • diff examples
  • export--Export sources from CVS, similar to checkout
    • export options
  • history--Show status of files and users
    • history options
  • import--Import sources into CVS, using vendor branches
    • import options
    • import output
    • import examples
  • log--Print out log information for files
    • log options
    • log examples
  • rdiff---'patch' format diffs between releases
    • rdiff options
    • rdiff examples
  • release--Indicate that a Module is no longer in use
    • release options
    • release output
    • release examples
  • update--Bring work tree in sync with repository
    • update options
    • update output
• Quick reference to CVS commands
• Reference manual for Administrative files
  • The modules file
    • Alias modules
    • Regular modules
    • Ampersand modules
    • Excluding directories
    • Module options
    • How the modules file "program options" programs are run
  • The cvswrappers file
  • The commit support files
    • The common syntax
  • Commitinfo
  • Verifying log messages
  • Editinfo
    • Editinfo example
  • Loginfo
    • Loginfo example
    • Keeping a checked out copy
  • Rcsinfo
  • Ignoring files via cvsignore
  • The checkoutlist file
  • The history file
  • Expansions in administrative files
  • The CVSROOT/config configuration file
• All environment variables which affect CVS
• Compatibility between CVS Versions
• Troubleshooting
  • Partial list of error messages
  • Trouble making a connection to a CVS server
  • Other common problems
• Credits
• Dealing with bugs in CVS or this manual
• Index