CVS--Concurrent Versions System
About this manual
Checklist for the impatient reader
Credits
BUGS
1 What is CVS?
CVS is not...
2 A sample session
2.1 Getting the source
2.2 Committing your changes
2.3 Cleaning up
2.4 Viewing differences
3 The Repository
3.1 Telling CVS where your repository is
3.2 How data is stored in the repository
3.2.1 Where files are stored within the repository
3.2.2 File permissions
3.2.3 The attic
3.3 How data is stored in the working directory
3.4 The administrative files
3.4.1 Editing administrative files
3.5 Multiple repositories
3.6 Creating a repository
3.7 Backing up a repository
3.8 Moving a repository
3.9 Remote repositories
3.9.1 Server requirements
3.9.2 Connecting with rsh
3.9.3 Direct connection with password authentication
3.9.3.1 Setting up the server for password authentication
3.9.3.2 Using the client with password authentication
3.9.3.3 Security considerations with password authentication
3.9.4 Direct connection with kerberos
3.10 Read-only repository access
3.11 Temporary directories for the server
4 Starting a project with CVS
4.1 Setting up the files
4.1.1 Creating a directory tree from a number of files
4.1.2 Creating Files From Other Version Control Systems
4.1.3 Creating a directory tree from scratch
4.2 Defining the module
5 Multiple developers
5.1 File status
5.2 Bringing a file up to date
5.3 Conflicts example
5.4 Informing others about commits
5.5 Several developers simultaneously attempting to run CVS
5.6 Mechanisms to track who is editing files
5.6.1 Telling CVS to watch certain files
5.6.2 Telling CVS to notify you
5.6.3 How to edit a file which is being watched
5.6.4 Information about who is watching and editing
5.6.5 Using watches with old versions of CVS
5.7 Choosing between reserved or unreserved checkouts
6 Revisions and branches
6.1 Revision numbers
6.2 Versions, revisions and releases
6.3 Assigning revisions
6.4 Tags--Symbolic revisions
6.5 What branches are good for
6.6 Creating a branch
6.7 Sticky tags
6.8 Magic branch numbers
7 Merging
7.1 Merging an entire branch
7.2 Merging from a branch several times
7.3 Merging differences between any two revisions
7.4 Merging can add or remove files
8 Recursive behavior
9 Adding files to a directory
10 Removing files
11 Removing directories
12 Tracking third-party sources
12.1 Importing a module for the first time
12.2 Updating a module with the import command
12.3 Reverting to the latest vendor release
12.4 How to handle binary files with cvs import
12.5 How to handle keyword substitution with cvs import
12.6 Multiple vendor branches
13 Moving and renaming files
13.1 The Normal way to Rename
13.2 Moving the history file
13.3 Copying the history file
14 Moving and renaming directories
15 History browsing
15.1 Log messages
15.2 The history database
15.3 User-defined logging
15.4 Annotate command
16 Keyword substitution
16.1 RCS Keywords
16.2 Using keywords
16.3 Avoiding substitution
16.4 Substitution modes
16.5 Problems with the $@asis{}Log$ keyword.
17 Handling binary files
18 How your build system interacts with CVS
19 Compatibility between CVS Versions
20 Revision management
20.1 When to commit?
A Guide to CVS commands
A.1 Overall structure of CVS commands
A.2 CVS's exit status
A.3 Default options and the ~/.cvsrc file
A.4 Global options
A.5 Common command options
A.6 admin--Administration front end for rcs
A.6.1 admin options
A.6.2 admin examples
A.6.2.1 Outdating is dangerous
A.6.2.2 Comment leaders
A.7 checkout--Check out sources for editing
A.7.1 checkout options
A.7.2 checkout examples
A.8 commit--Check files into the repository
A.8.1 commit options
A.8.2 commit examples
A.8.2.1 Committing to a branch
A.8.2.2 Creating the branch after editing
A.9 diff--Show differences between revisions
A.9.1 diff options
A.9.2 diff examples
A.10 export--Export sources from CVS, similar to checkout
A.10.1 export options
A.11 history--Show status of files and users
A.11.1 history options
A.12 import--Import sources into CVS, using vendor branches
A.12.1 import options
A.12.2 import output
A.12.3 import examples
A.13 log--Print out log information for files
A.13.1 log options
A.13.2 log examples
A.14 rdiff---'patch' format diffs between releases
A.14.1 rdiff options
A.14.2 rdiff examples
A.15 release--Indicate that a Module is no longer in use
A.15.1 release options
A.15.2 release output
A.15.3 release examples
A.16 rtag--Add a symbolic tag to a module
A.16.1 rtag options
A.17 tag--Add a symbolic tag to checked out versions of files
A.17.1 tag options
A.18 update--Bring work tree in sync with repository
A.18.1 update options
A.18.2 update output
B Quick reference to CVS commands
C Reference manual for Administrative files
C.1 The modules file
C.2 The cvswrappers file
C.3 The commit support files
C.3.1 The common syntax
C.4 Commitinfo
C.5 Verifying log messages
C.6 Editinfo
C.6.1 Editinfo example
C.7 Loginfo
C.7.1 Loginfo example
C.7.2 Keeping a checked out copy
C.8 Rcsinfo
C.9 Ignoring files via cvsignore
C.10 The history file
C.11 Expansions in administrative files
D All environment variables which affect CVS
E Troubleshooting
E.1 Partial list of error messages
E.2 Other common problems
F GNU GENERAL PUBLIC LICENSE
Preamble
How to Apply These Terms to Your New Programs
Index
This document was generated on 5 March 1998 using the
texi2html
translator version 1.51.