|
Check-in Number:
|
3752 | |
| Date: |
2000-Jun-13 11:11:07 (local)
2000-Jun-13 09:11:07 (UTC) |
| User: | ossp |
| Branch: | |
| Comment: |
initial checkin |
| Tickets: |
|
| Inspections: |
|
| Files: |
|
CVSROOT/admininfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,15 ----
+ # The "admininfo" file is used to control pre-admin 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 admin operation 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".
|
|
CVSROOT/checkoutlist -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,13 ----
+ # 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 '#'
|
|
CVSROOT/commitinfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,15 ----
+ # 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".
|
|
CVSROOT/config -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,25 ----
+ # Set this to "no" if pserver shouldn't check system users/passwords
+ #SystemAuth=no
+
+ # Set `PreservePermissions' to `yes' to save file status information
+ # in the repository.
+ #PreservePermissions=no
+
+ # Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
+ # level of the new working directory when using the `cvs checkout'
+ # command.
+ #TopLevelAdmin=no
+
+ # Set `LogHistory' to `all' or `TOFEWGCMAR' to log all transactions to the
+ # history file, or a subset as needed (ie `TMAR' logs all write operations)
+ #LogHistory=TOFEWGCMAR
+
+ # Set `HistoryFile' to the path name (relative to CVSROOT) of the history file
+ # if you do not want to store it not under CVSROOT/history
+ #HistoryFile=CVSROOT/history
+
+ # Set `LocalIdName' to the name of a local tag to use in addition to Id
+ #LocalIdName=LocalId
+
+ # Set `UMask' to the octal value of the umask.
+ #UMask=002
|
|
CVSROOT/cvswrappers -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,23 ----
+ # This file affects handling of files based on their names.
+ #
+ # The -t/-f options allow one to treat directories of files
+ # as a single file, or to transform a file in other ways on
+ # its way in and out of CVS.
+ #
+ # The -m option specifies whether CVS attempts to merge files.
+ #
+ # The -k option specifies keyword expansion (e.g. -kb for binary).
+ #
+ # Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
+ #
+ # wildcard [option value][option value]...
+ #
+ # where option is one of
+ # -f from cvs filter value: path to filter
+ # -t to cvs filter value: path to filter
+ # -m update methodology value: MERGE or COPY
+ # -k expansion mode value: b, o, kkv, &c
+ #
+ # and value is a single-quote delimited value.
+ # For example:
+ #*.gif -k 'b'
|
|
CVSROOT/editinfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,21 ----
+ # 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.
|
|
CVSROOT/importinfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,15 ----
+ # The "importinfo" file is used to control pre-import checks.
+ # The filter on the right is invoked with the repository to check.
+ # A non-zero exit of the filter program will cause the import
+ # operation 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".
|
|
CVSROOT/loginfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,26 ----
+ # 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
|
|
CVSROOT/modules -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,26 ----
+ # Three different line formats are valid:
+ # key -a aliases...
+ # key [options] directory
+ # key [options] directory files...
+ #
+ # Where "options" are composed of:
+ # -i prog Run "prog" on "cvs commit" from top-level of module.
+ # -o prog Run "prog" on "cvs checkout" of module.
+ # -e prog Run "prog" on "cvs export" of module.
+ # -t prog Run "prog" on "cvs rtag" of module.
+ # -u prog Run "prog" on "cvs update" of module.
+ # -d dir Place module in directory "dir" instead of module name.
+ # -l Top-level directory only -- do not recurse.
+ #
+ # NOTE: If you change any of the "Run" options above, you'll have to
+ # release and re-checkout any working directories of these modules.
+ #
+ # And "directory" is a path to a directory relative to $CVSROOT.
+ #
+ # The "-a" option specifies an alias. An alias is interpreted as if
+ # everything on the right of the "-a" had been typed on the command line.
+ #
+ # You can encode a module within a module by using the special '&'
+ # character to interpose another module into the current module. This
+ # can be useful for creating a module that consists of many directories
+ # spread out over the entire source repository.
|
|
CVSROOT/notify -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,12 ----
+ # 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"
|
|
CVSROOT/rcsinfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,13 ----
+ # The "rcsinfo" file is used to control templates with which the editor
+ # is invoked on commit and import.
+ #
+ # 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. For the first match that is found, then the remainder of the
+ # line is the name of the file that contains the template.
+ #
+ # 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".
|
|
CVSROOT/taginfo -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,20 ----
+ # The "taginfo" file is used to control pre-tag checks.
+ # The filter on the right is invoked with the following arguments:
+ #
+ # $1 -- tagname
+ # $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
+ # $3 -- repository
+ # $4-> file revision [file revision ...]
+ #
+ # A non-zero exit of the filter program will cause the tag 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".
|
|
CVSROOT/verifymsg -> 1.1
*** /dev/null Sat Nov 23 01:02:23 2024
--- - Sat Nov 23 01:02:49 2024
***************
*** 0 ****
--- 1,21 ----
+ # The "verifymsg" 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.
|
|
