summaryrefslogtreecommitdiff
path: root/CVSROOT
diff options
context:
space:
mode:
authorBjörn Stenberg <bjorn@haxx.se>2002-01-17 16:11:26 +0000
committerBjörn Stenberg <bjorn@haxx.se>2002-01-17 16:11:26 +0000
commit2daf14965c39bc911793520a90027797ad92df74 (patch)
tree8e83c67f2b86e7f0823f4fc3273ff65a081bb8c1 /CVSROOT
parente196759fbd5142d1197320f62b33022f3b80ef98 (diff)
downloadrockbox-2daf14965c39bc911793520a90027797ad92df74.tar.gz
rockbox-2daf14965c39bc911793520a90027797ad92df74.zip
initial checkin
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@3 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'CVSROOT')
-rw-r--r--CVSROOT/cvswrappers23
-rw-r--r--CVSROOT/editinfo21
-rw-r--r--CVSROOT/notify12
-rw-r--r--CVSROOT/rcsinfo13
-rw-r--r--CVSROOT/taginfo20
-rw-r--r--CVSROOT/verifymsg21
6 files changed, 110 insertions, 0 deletions
diff --git a/CVSROOT/cvswrappers b/CVSROOT/cvswrappers
new file mode 100644
index 0000000000..0accaf1b15
--- /dev/null
+++ b/CVSROOT/cvswrappers
@@ -0,0 +1,23 @@
1# This file affects handling of files based on their names.
2#
3# The -t/-f options allow one to treat directories of files
4# as a single file, or to transform a file in other ways on
5# its way in and out of CVS.
6#
7# The -m option specifies whether CVS attempts to merge files.
8#
9# The -k option specifies keyword expansion (e.g. -kb for binary).
10#
11# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
12#
13# wildcard [option value][option value]...
14#
15# where option is one of
16# -f from cvs filter value: path to filter
17# -t to cvs filter value: path to filter
18# -m update methodology value: MERGE or COPY
19# -k expansion mode value: b, o, kkv, &c
20#
21# and value is a single-quote delimited value.
22# For example:
23#*.gif -k 'b'
diff --git a/CVSROOT/editinfo b/CVSROOT/editinfo
new file mode 100644
index 0000000000..d78886c152
--- /dev/null
+++ b/CVSROOT/editinfo
@@ -0,0 +1,21 @@
1# The "editinfo" file is used to allow verification of logging
2# information. It works best when a template (as specified in the
3# rcsinfo file) is provided for the logging procedure. Given a
4# template with locations for, a bug-id number, a list of people who
5# reviewed the code before it can be checked in, and an external
6# process to catalog the differences that were code reviewed, the
7# following test can be applied to the code:
8#
9# Making sure that the entered bug-id number is correct.
10# Validating that the code that was reviewed is indeed the code being
11# checked in (using the bug-id number or a seperate review
12# number to identify this particular code set.).
13#
14# If any of the above test failed, then the commit would be aborted.
15#
16# Actions such as mailing a copy of the report to each reviewer are
17# better handled by an entry in the loginfo file.
18#
19# One thing that should be noted is the the ALL keyword is not
20# supported. There can be only one entry that matches a given
21# repository.
diff --git a/CVSROOT/notify b/CVSROOT/notify
new file mode 100644
index 0000000000..34f0bc2888
--- /dev/null
+++ b/CVSROOT/notify
@@ -0,0 +1,12 @@
1# The "notify" file controls where notifications from watches set by
2# "cvs watch add" or "cvs edit" are sent. The first entry on a line is
3# a regular expression which is tested against the directory that the
4# change is being made to, relative to the $CVSROOT. If it matches,
5# then the remainder of the line is a filter program that should contain
6# one occurrence of %s for the user to notify, and information on its
7# standard input.
8#
9# "ALL" or "DEFAULT" can be used in place of the regular expression.
10#
11# For example:
12#ALL mail %s -s "CVS notification"
diff --git a/CVSROOT/rcsinfo b/CVSROOT/rcsinfo
new file mode 100644
index 0000000000..49e59f4d0d
--- /dev/null
+++ b/CVSROOT/rcsinfo
@@ -0,0 +1,13 @@
1# The "rcsinfo" file is used to control templates with which the editor
2# is invoked on commit and import.
3#
4# The first entry on a line is a regular expression which is tested
5# against the directory that the change is being made to, relative to the
6# $CVSROOT. For the first match that is found, then the remainder of the
7# line is the name of the file that contains the template.
8#
9# If the repository name does not match any of the regular expressions in this
10# file, the "DEFAULT" line is used, if it is specified.
11#
12# If the name "ALL" appears as a regular expression it is always used
13# in addition to the first matching regex or "DEFAULT".
diff --git a/CVSROOT/taginfo b/CVSROOT/taginfo
new file mode 100644
index 0000000000..274a46dd5b
--- /dev/null
+++ b/CVSROOT/taginfo
@@ -0,0 +1,20 @@
1# The "taginfo" file is used to control pre-tag checks.
2# The filter on the right is invoked with the following arguments:
3#
4# $1 -- tagname
5# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
6# $3 -- repository
7# $4-> file revision [file revision ...]
8#
9# A non-zero exit of the filter program will cause the tag to be aborted.
10#
11# The first entry on a line is a regular expression which is tested
12# against the directory that the change is being committed to, relative
13# to the $CVSROOT. For the first match that is found, then the remainder
14# of the line is the name of the filter to run.
15#
16# If the repository name does not match any of the regular expressions in this
17# file, the "DEFAULT" line is used, if it is specified.
18#
19# If the name "ALL" appears as a regular expression it is always used
20# in addition to the first matching regex or "DEFAULT".
diff --git a/CVSROOT/verifymsg b/CVSROOT/verifymsg
new file mode 100644
index 0000000000..86f747ce22
--- /dev/null
+++ b/CVSROOT/verifymsg
@@ -0,0 +1,21 @@
1# The "verifymsg" file is used to allow verification of logging
2# information. It works best when a template (as specified in the
3# rcsinfo file) is provided for the logging procedure. Given a
4# template with locations for, a bug-id number, a list of people who
5# reviewed the code before it can be checked in, and an external
6# process to catalog the differences that were code reviewed, the
7# following test can be applied to the code:
8#
9# Making sure that the entered bug-id number is correct.
10# Validating that the code that was reviewed is indeed the code being
11# checked in (using the bug-id number or a seperate review
12# number to identify this particular code set.).
13#
14# If any of the above test failed, then the commit would be aborted.
15#
16# Actions such as mailing a copy of the report to each reviewer are
17# better handled by an entry in the loginfo file.
18#
19# One thing that should be noted is the the ALL keyword is not
20# supported. There can be only one entry that matches a given
21# repository.