Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

This commit was manufactured by cvs2svn to create tag 'REL_0_8_11'.

git-svn-id: http://rubygems.rubyforge.org/svn/tags/REL_0_8_11@924 3d4018f9-ac1a-0410-99e9-8a154d859a19
  • Loading branch information...
commit bc954b234825ae384c21facf0edbb526a34c7e6a 1 parent 44c5581
(no author) authored
13 CVSROOT/checkoutlist
... ... @@ -1,13 +0,0 @@
1   -# The "checkoutlist" file is used to support additional version controlled
2   -# administrative files in $CVSROOT/CVSROOT, such as template files.
3   -#
4   -# The first entry on a line is a filename which will be checked out from
5   -# the corresponding RCS file in the $CVSROOT/CVSROOT directory.
6   -# The remainder of the line is an error message to use if the file cannot
7   -# be checked out.
8   -#
9   -# File format:
10   -#
11   -# [<whitespace>]<filename><whitespace><error message><end-of-line>
12   -#
13   -# comment lines begin with '#'
15 CVSROOT/commitinfo
... ... @@ -1,15 +0,0 @@
1   -# The "commitinfo" file is used to control pre-commit checks.
2   -# The filter on the right is invoked with the repository and a list
3   -# of files to check. A non-zero exit of the filter program will
4   -# cause the commit to be aborted.
5   -#
6   -# The first entry on a line is a regular expression which is tested
7   -# against the directory that the change is being committed to, relative
8   -# to the $CVSROOT. For the first match that is found, then the remainder
9   -# of the line is the name of the filter to run.
10   -#
11   -# If the repository name does not match any of the regular expressions in this
12   -# file, the "DEFAULT" line is used, if it is specified.
13   -#
14   -# If the name "ALL" appears as a regular expression it is always used
15   -# in addition to the first matching regex or "DEFAULT".
21 CVSROOT/config
... ... @@ -1,21 +0,0 @@
1   -# Set this to "no" if pserver shouldn't check system users/passwords
2   -#SystemAuth=no
3   -
4   -# Put CVS lock files in this directory rather than directly in the repository.
5   -LockDir=/var/cvslocks/
6   -
7   -# Set `TopLevelAdmin' to `yes' to create a CVS directory at the top
8   -# level of the new working directory when using the `cvs checkout'
9   -# command.
10   -#TopLevelAdmin=no
11   -
12   -# Set `LogHistory' to `all' or `TOFEWGCMAR' to log all transactions to the
13   -# history file, or a subset as needed (ie `TMAR' logs all write operations)
14   -#LogHistory=TOFEWGCMAR
15   -
16   -# Set `RereadLogAfterVerify' to `always' (the default) to allow the verifymsg
17   -# script to change the log message. Set it to `stat' to force CVS to verify# that the file has changed before reading it (this can take up to an extra
18   -# second per directory being committed, so it is not recommended for large
19   -# repositories. Set it to `never' (the previous CVS behavior) to prevent
20   -# verifymsg scripts from changing the log message.
21   -#RereadLogAfterVerify=always
75 CVSROOT/cvswrappers
... ... @@ -1,75 +0,0 @@
1   -# This file affects handling of files based on their names.
2   -#
3   -# The -m option specifies whether CVS attempts to merge files.
4   -#
5   -# The -k option specifies keyword expansion (e.g. -kb for binary).
6   -#
7   -# Format of wrapper file ($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)
8   -#
9   -# wildcard [option value][option value]...
10   -#
11   -# where option is one of
12   -# -f from cvs filter value: path to filter
13   -# -t to cvs filter value: path to filter
14   -# -m update methodology value: MERGE or COPY
15   -# -k expansion mode value: b, o, kkv, &c
16   -#
17   -# and value is a single-quote delimited value.
18   -# For example:
19   -#*.gif -k 'b'
20   -*.JPG -k 'b' -m 'COPY'
21   -*.avi -k 'b' -m 'COPY'
22   -*.bin -k 'b' -m 'COPY'
23   -*.bz -k 'b' -m 'COPY'
24   -*.bz2 -k 'b' -m 'COPY'
25   -*.doc -k 'b' -m 'COPY'
26   -*.exe -k 'b' -m 'COPY'
27   -*.gif -k 'b' -m 'COPY'
28   -*.gz -k 'b' -m 'COPY'
29   -*.hqx -k 'b' -m 'COPY'
30   -*.jar -k 'b' -m 'COPY'
31   -*.jpeg -k 'b' -m 'COPY'
32   -*.jpg -k 'b' -m 'COPY'
33   -*.mov -k 'b' -m 'COPY'
34   -*.mp3 -k 'b' -m 'COPY'
35   -*.mpg -k 'b' -m 'COPY'
36   -*.pdf -k 'b' -m 'COPY'
37   -*.png -k 'b' -m 'COPY'
38   -*.ppt -k 'b' -m 'COPY'
39   -*.rpm -k 'b' -m 'COPY'
40   -*.sit -k 'b' -m 'COPY'
41   -*.srpm -k 'b' -m 'COPY'
42   -*.swf -k 'b' -m 'COPY'
43   -*.tar -k 'b' -m 'COPY'
44   -*.tbz -k 'b' -m 'COPY'
45   -*.tgz -k 'b' -m 'COPY'
46   -*.tif -k 'b' -m 'COPY'
47   -*.tiff -k 'b' -m 'COPY'
48   -*.xbm -k 'b' -m 'COPY'
49   -*.xls -k 'b' -m 'COPY'
50   -*.zip -k 'b' -m 'COPY'
51   -*.keystore -k 'b' -m 'COPY'
52   -# File types added by Borland JBuilder
53   -*.aiff -k 'b'
54   -*.midi -k 'b'
55   -*.jds -k 'b'
56   -*.asx -k 'b'
57   -*.wav -k 'b'
58   -*.war -k 'b'
59   -*.ear -k 'b'
60   -*.obj -k 'b'
61   -*.dcu -k 'b'
62   -*.class -k 'b'
63   -*.au -k 'b'
64   -*.eargrp -k 'b'
65   -*.jpe -k 'b'
66   -*.o -k 'b'
67   -*.asf -k 'b'
68   -*.rar -k 'b'
69   -*.library -k 'b'
70   -*.ejbgrp -k 'b'
71   -*.ram -k 'b'
72   -*.ejbgrpx -k 'b'
73   -*.mid -k 'b'
74   -*.rmf -k 'b'
75   -
21 CVSROOT/editinfo
... ... @@ -1,21 +0,0 @@
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.
27 CVSROOT/loginfo
... ... @@ -1,27 +0,0 @@
1   -# The "loginfo" file controls where "cvs commit" log information
2   -# is sent. The first entry on a line is a regular expression which must match
3   -# the directory that the change is being made to, relative to the
4   -# $CVSROOT. If a match is found, then the remainder of the line is a filter
5   -# program that should expect log information on its standard input.
6   -#
7   -# If the repository name does not match any of the regular expressions in this
8   -# file, the "DEFAULT" line is used, if it is specified.
9   -#
10   -# If the name ALL appears as a regular expression it is always used
11   -# in addition to the first matching regex or DEFAULT.
12   -#
13   -# You may specify a format string as part of the
14   -# filter. The string is composed of a `%' followed
15   -# by a single format character, or followed by a set of format
16   -# characters surrounded by `{' and `}' as separators. The format
17   -# characters are:
18   -#
19   -# s = file name
20   -# V = old version number (pre-checkin)
21   -# v = new version number (post-checkin)
22   -#
23   -# For example:
24   -#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
25   -# or
26   -#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
27   -DEFAULT /var/cvs/commitmailer.sh %s jim-keyword-cvsrubygems.4be010@weirichhouse.org
26 CVSROOT/modules
... ... @@ -1,26 +0,0 @@
1   -# Three different line formats are valid:
2   -# key -a aliases...
3   -# key [options] directory
4   -# key [options] directory files...
5   -#
6   -# Where "options" are composed of:
7   -# -i prog Run "prog" on "cvs commit" from top-level of module.
8   -# -o prog Run "prog" on "cvs checkout" of module.
9   -# -e prog Run "prog" on "cvs export" of module.
10   -# -t prog Run "prog" on "cvs rtag" of module.
11   -# -u prog Run "prog" on "cvs update" of module.
12   -# -d dir Place module in directory "dir" instead of module name.
13   -# -l Top-level directory only -- do not recurse.
14   -#
15   -# NOTE: If you change any of the "Run" options above, you'll have to
16   -# release and re-checkout any working directories of these modules.
17   -#
18   -# And "directory" is a path to a directory relative to $CVSROOT.
19   -#
20   -# The "-a" option specifies an alias. An alias is interpreted as if
21   -# everything on the right of the "-a" had been typed on the command line.
22   -#
23   -# You can encode a module within a module by using the special '&'
24   -# character to interpose another module into the current module. This
25   -# can be useful for creating a module that consists of many directories
26   -# spread out over the entire source repository.
12 CVSROOT/notify
... ... @@ -1,12 +0,0 @@
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 "CVS notification" %s
1  CVSROOT/passwd
... ... @@ -1 +0,0 @@
1   -anonymous:$1$0H$2/LSjjwDfsSA0gaDYY5Df/:tutorials
13 CVSROOT/rcsinfo
... ... @@ -1,13 +0,0 @@
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".
2  CVSROOT/readers
... ... @@ -1,2 +0,0 @@
1   -anonymous::anonymous
2   -
20 CVSROOT/taginfo
... ... @@ -1,20 +0,0 @@
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".
21 CVSROOT/verifymsg
... ... @@ -1,21 +0,0 @@
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.

0 comments on commit bc954b2

Please sign in to comment.
Something went wrong with that request. Please try again.