CVS--Concurrent Versions System

• About this manual
  • Checklist for the impatient reader
  • Credits
  • BUGS
• What is CVS?
  • CVS is 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
    • The attic
  • 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 kerberos
  • 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
• 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
• Revisions and branches
  • Revision numbers
  • Versions, revisions and releases
  • Assigning revisions
  • Tags--Symbolic revisions
  • What branches are good for
  • Creating a branch
  • Sticky tags
  • Magic branch numbers
• Merging
  • Merging an entire branch
  • Merging from a branch several times
  • Merging differences between any two revisions
  • Merging can add or remove files
• Recursive behavior
• Adding files to a directory
• Removing files
• Removing directories
• Tracking third-party sources
  • Importing a module for the first time
  • Updating a module 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
• 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
• Keyword substitution
  • RCS Keywords
  • Using keywords
  • Avoiding substitution
  • Substitution modes
  • Problems with the $@asis{}Log$ keyword.
• Handling binary files
• How your build system interacts with CVS
• Compatibility between CVS Versions
• Revision management
  • When to commit?
• 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 front end for rcs
    • admin options
    • admin examples
      • Outdating is dangerous
      • Comment leaders
  • 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
  • rtag--Add a symbolic tag to a module
    • rtag options
  • tag--Add a symbolic tag to checked out versions of files
    • tag options
  • 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
  • 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 history file
  • Expansions in administrative files
• All environment variables which affect CVS
• Troubleshooting
  • Partial list of error messages
  • Other common problems
• GNU GENERAL PUBLIC LICENSE
  • Preamble
  • How to Apply These Terms to Your New Programs
• Index

This document was generated on 15 August 1997 using the texi2html translator version 1.51.