DESCRIPTION
cvs is a system for providing source control to hierarchical collections of source directories. Commands and procedures for using
cvs are described in
cvs(
1).
cvs manages
source repositories, the directories containing master copies of the revision-controlled files, by copying particular revisions of the files to (and modifications back from) developers' private
working directories. In terms of file structure, each individual source repository is an immediate subdirectory of
$CVSROOT.
The files described here are supporting files; they do not have to exist for
cvs to operate, but they allow you to make
cvs operation more flexible.
You can use the `modules' file to define symbolic names for collections of source maintained with
cvs. If there is no `modules' file, developers must specify complete path names (absolute, or relative to
$CVSROOT) for the files they wish to manage with
cvs commands.
You can use the `commitinfo' file to define programs to execute whenever `
cvs commit' is about to execute. These programs are used for ``pre-commit'' checking to verify that the modified, added, and removed files are really ready to be committed. Some uses for this check might be to turn off a portion (or all) of the source repository from a particular person or group. Or, perhaps, to verify that the changed files conform to the site's standards for coding practice.
You can use the `cvswrappers' file to record
cvs wrapper commands to be used when checking files into and out of the repository. Wrappers allow the file or directory to be processed on the way in and out of CVS. The intended uses are many, one possible use would be to reformat a C file before the file is checked in, so all of the code in the repository looks the same.
You can use the `loginfo' file to define programs to execute after any
commit, which writes a log entry for changes in the repository. These logging programs might be used to append the log message to a file. Or send the log message through electronic mail to a group of developers. Or, perhaps, post the log message to a particular newsgroup.
You can use the `taginfo' file to define programs to execute after any
tagor
rtag operation. These programs might be used to append a message to a file listing the new tag name and the programmer who created it, or send mail to a group of developers, or, perhaps, post a message to a particular newsgroup.
You can use the `rcsinfo' file to define forms for log messages.
You can use the `editinfo' file to define a program to execute for editing/validating `
cvs commit' log entries. This is most useful when used with a `rcsinfo' forms specification, as it can verify that the proper fields of the form have been filled in by the user committing the change.
You can use the `cvsignore' file to specify the default list of files to ignore during
update.
You can use the `history' file to record the
cvs commands that affect the repository. The creation of this file enables history logging.
COPYING
Copyright © 1992 Cygnus Support, Brian Berliner, and Jeff Polk
Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies.
Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English.