initial checkin

# The "checkoutlist" file is used to support additional version controlled

# administrative files in $CVSROOT/CVSROOT, such as template files.

#

# The first entry on a line is a filename which will be checked out from

# the corresponding RCS file in the $CVSROOT/CVSROOT directory.

# The remainder of the line is an error message to use if the file cannot

# be checked out.

#

# File format:

#

#	[<whitespace>]<filename><whitespace><error message><end-of-line>

#

# comment lines begin with '#'

# The "commitinfo" file is used to control pre-commit checks.

# The filter on the right is invoked with the repository and a list 

# of files to check.  A non-zero exit of the filter program will 

# cause the commit to be aborted.

#

# The first entry on a line is a regular expression which is tested

# against the directory that the change is being committed to, relative

# to the $CVSROOT.  For the first match that is found, then the remainder

# of the line is the name of the filter to run.

#

# If the repository name does not match any of the regular expressions in this

# file, the "DEFAULT" line is used, if it is specified.

#

# If the name "ALL" appears as a regular expression it is always used

# in addition to the first matching regex or "DEFAULT".

# The "editinfo" file is used to allow verification of logging

# information.  It works best when a template (as specified in the

# rcsinfo file) is provided for the logging procedure.  Given a

# template with locations for, a bug-id number, a list of people who

# reviewed the code before it can be checked in, and an external

# process to catalog the differences that were code reviewed, the

# following test can be applied to the code:

#

#   Making sure that the entered bug-id number is correct.

#   Validating that the code that was reviewed is indeed the code being

#       checked in (using the bug-id number or a seperate review

#       number to identify this particular code set.).

#

# If any of the above test failed, then the commit would be aborted.

#

# Actions such as mailing a copy of the report to each reviewer are

# better handled by an entry in the loginfo file.

#

# One thing that should be noted is the the ALL keyword is not

# supported.  There can be only one entry that matches a given

# repository.

# The "loginfo" file controls where "cvs commit" log information

# is sent.  The first entry on a line is a regular expression which must match

# the directory that the change is being made to, relative to the

# $CVSROOT.  If a match is found, then the remainder of the line is a filter

# program that should expect log information on its standard input.

#

# If the repository name does not match any of the regular expressions in this

# file, the "DEFAULT" line is used, if it is specified.

#

# If the name ALL appears as a regular expression it is always used

# in addition to the first matching regex or DEFAULT.

#

# You may specify a format string as part of the

# filter.  The string is composed of a `%' followed

# by a single format character, or followed by a set of format

# characters surrounded by `{' and `}' as separators.  The format

# characters are:

#

#   s = file name

#   V = old version number (pre-checkin)

#   v = new version number (post-checkin)

#

# For example:

#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog

# or

#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog

# The "notify" file controls where notifications from watches set by

# "cvs watch add" or "cvs edit" are sent.  The first entry on a line is

# a regular expression which is tested against the directory that the

# change is being made to, relative to the $CVSROOT.  If it matches,

# then the remainder of the line is a filter program that should contain

# one occurrence of %s for the user to notify, and information on its

# standard input.

#

# "ALL" or "DEFAULT" can be used in place of the regular expression.

#

# For example:

#ALL mail %s -s "CVS notification"