You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-commits@maven.apache.org by tr...@apache.org on 2004/07/02 18:42:21 UTC
cvs commit: maven-scm/scm-providers/cvslib/src/test/repository/test-repo/checkout Foo.java,v Readme.txt,v
trygvis 2004/07/02 09:42:21
Added: scm-providers/cvslib/src/test/repository/CVSROOT
checkoutlist checkoutlist,v commitinfo commitinfo,v
config config,v cvswrappers cvswrappers,v history
loginfo loginfo,v modules modules,v notify notify,v
rcsinfo rcsinfo,v taginfo taginfo,v val-tags
verifymsg verifymsg,v
scm-providers/cvslib/src/test/repository/test-repo/checkout
Foo.java,v Readme.txt,v
Log:
o Adding a CVS repository thats used for testing.
Revision Changes Path
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/checkoutlist
Index: checkoutlist
===================================================================
# 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 '#'
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/checkoutlist,v
Index: checkoutlist,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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 '#'
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/commitinfo
Index: commitinfo
===================================================================
# 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.
#
# Format strings present in the filter will be replaced as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %{s} = file name, file name, ...
#
# If no format strings are present in the filter string, a default of
# " %r %s" will be appended to the filter string, but this usage is
# deprecated.
#
# 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".
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/commitinfo,v
Index: commitinfo,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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.
#
# Format strings present in the filter will be replaced as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %{s} = file name, file name, ...
#
# If no format strings are present in the filter string, a default of
# " %r %s" will be appended to the filter string, but this usage is
# deprecated.
#
# 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".
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/config
Index: config
===================================================================
# Set this to "no" if pserver shouldn't check system users/passwords
#SystemAuth=no
# Put CVS lock files in this directory rather than directly in the repository.
#LockDir=/var/lock/cvs
# 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 `TOEFWUPCGMAR' to log all transactions to the
# history file, or a subset as needed (ie `TMAR' logs all write operations)
#LogHistory=TOEFWUPCGMAR
# Set `RereadLogAfterVerify' to `always' (the default) to allow the verifymsg
# 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
# second per directory being committed, so it is not recommended for large
# repositories. Set it to `never' (the previous CVS behavior) to prevent
# verifymsg scripts from changing the log message.
#RereadLogAfterVerify=always
# Set `UserAdminOptions' to the list of `cvs admin' commands (options)
# that users not in the `cvsadmin' group are allowed to run. This
# defaults to `k', or only allowing the changing of the default
# keyword expansion mode for files for users not in the `cvsadmin' group.
# This value is ignored if the `cvsadmin' group does not exist.
#
# The following string would enable all `cvs admin' commands for all
# users:
#UserAdminOptions=aAbceIklLmnNostuU
# Set `UseNewInfoFmtStrings' to `no' if you must support a legacy system by
# enabling the deprecated old style info file command line format strings.
# Be warned that these strings could be disabled in any new version of CVS.
UseNewInfoFmtStrings=yes
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/config,v
Index: config,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# Set this to "no" if pserver shouldn't check system users/passwords
#SystemAuth=no
# Put CVS lock files in this directory rather than directly in the repository.
#LockDir=/var/lock/cvs
# 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 `TOEFWUPCGMAR' to log all transactions to the
# history file, or a subset as needed (ie `TMAR' logs all write operations)
#LogHistory=TOEFWUPCGMAR
# Set `RereadLogAfterVerify' to `always' (the default) to allow the verifymsg
# 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
# second per directory being committed, so it is not recommended for large
# repositories. Set it to `never' (the previous CVS behavior) to prevent
# verifymsg scripts from changing the log message.
#RereadLogAfterVerify=always
# Set `UserAdminOptions' to the list of `cvs admin' commands (options)
# that users not in the `cvsadmin' group are allowed to run. This
# defaults to `k', or only allowing the changing of the default
# keyword expansion mode for files for users not in the `cvsadmin' group.
# This value is ignored if the `cvsadmin' group does not exist.
#
# The following string would enable all `cvs admin' commands for all
# users:
#UserAdminOptions=aAbceIklLmnNostuU
# Set `UseNewInfoFmtStrings' to `no' if you must support a legacy system by
# enabling the deprecated old style info file command line format strings.
# Be warned that these strings could be disabled in any new version of CVS.
UseNewInfoFmtStrings=yes
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/cvswrappers
Index: cvswrappers
===================================================================
# This file affects handling of files based on their names.
#
# 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'
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/cvswrappers,v
Index: cvswrappers,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# This file affects handling of files based on their names.
#
# 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'
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/history
Index: history
===================================================================
O40d9d82c|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/*0|test-repo||test-repo
O40d9d88a|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvslib/update/*0|test-repo||test-repo
U40d9d88b|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvslib/update/*0|test-repo/checkout|1.1|Foo.java
O40d9d945|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvslib/update/*0|test-repo||test-repo
U40d9d945|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvslib/update/*0|test-repo/checkout|1.1|Foo.java
O40d9dad4|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
O40d9dae1|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
O40d9dbb9|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
O40d9dbdb|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
O40d9dbfd|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
U40d9dbfe|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9dc78|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
U40d9dc79|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9df3c|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
U40d9df3d|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9e0f3|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
U40d9e0f4|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9eb2d|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo||test-repo
U40d9eb2e|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/testrepo/cvs/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9ebf3|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo||test-repo
U40d9ebf4|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9ecbc|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest/testGetCommand/*0|test-repo||test-repo
O40d9ee16|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest/testGetCommand/*0|test-repo||test-repo
O40d9ee17|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo||test-repo
U40d9ee18|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9ef00|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest/testGetCommand/*0|test-repo||test-repo
O40d9ef01|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo||test-repo
U40d9ef02|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40d9efb3|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest/testGetCommand/*0|test-repo||test-repo
O40d9efb4|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo||test-repo
U40d9efb5|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40dbb28f|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo||test-repo
U40dbb290|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40dbb291|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest/testGetCommand/*0|test-repo||test-repo
O40e1e618|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo||test-repo
U40e1e619|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.update.CvsUpdateCommandTest/testCommand/*0|test-repo/checkout|1.1|Foo.java
O40e1e61a|trygvis|~/jakarta/maven-scm/scm-providers/cvslib/target/workingDirectory/org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest/testGetCommand/*0|test-repo||test-repo
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/loginfo
Index: loginfo
===================================================================
# 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.
#
# If any format strings are present in the filter, they will be replaced as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %{sVv} = attribute list = file name, old version number (pre-checkin),
# new version number (post-checkin). When either old or new revision is
# unknown, doesn't exist, or isn't applicable, the string "NONE" will be
# placed on the command line instead.
#
# Note that %{sVv} is a list operator and not all elements are necessary. Thus %{sv} is
# a legal format string, but will only be replaced with file name and new revision.
# it also generates multiple arguments for each file being operated upon. i.e. if two
# files, file1 & file2, are being commited from 1.1 to version 1.1.2.1 and from 1.1.2.2
# to 1.1.2.3, respectively, %{sVv} will generate the following six arguments in this
# order: file1, 1.1, 1.1.2.1, file2, 1.1.2.2, 1.1.2.3.
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/loginfo,v
Index: loginfo,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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.
#
# If any format strings are present in the filter, they will be replaced as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %{sVv} = attribute list = file name, old version number (pre-checkin),
# new version number (post-checkin). When either old or new revision is
# unknown, doesn't exist, or isn't applicable, the string "NONE" will be
# placed on the command line instead.
#
# Note that %{sVv} is a list operator and not all elements are necessary. Thus %{sv} is
# a legal format string, but will only be replaced with file name and new revision.
# it also generates multiple arguments for each file being operated upon. i.e. if two
# files, file1 & file2, are being commited from 1.1 to version 1.1.2.1 and from 1.1.2.2
# to 1.1.2.3, respectively, %{sVv} will generate the following six arguments in this
# order: file1, 1.1, 1.1.2.1, file2, 1.1.2.2, 1.1.2.3.
#
# For example:
#DEFAULT (echo ""; id; echo %s; date; cat) >> $CVSROOT/CVSROOT/commitlog
# or
#DEFAULT (echo ""; id; echo %{sVv}; date; cat) >> $CVSROOT/CVSROOT/commitlog
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/modules
Index: modules
===================================================================
# 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.
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/modules,v
Index: modules,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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.
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/notify
Index: notify
===================================================================
# 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.
#
# format strings are replaceed as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %s = user to notify
#
# For example:
#ALL (echo Committed to %r/%p; cat) |mail %s -s "CVS notification"
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/notify,v
Index: notify,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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.
#
# format strings are replaceed as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %s = user to notify
#
# For example:
#ALL (echo Committed to %r/%p; cat) |mail %s -s "CVS notification"
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/rcsinfo
Index: rcsinfo
===================================================================
# 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".
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/rcsinfo,v
Index: rcsinfo,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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".
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/taginfo
Index: taginfo
===================================================================
# The "taginfo" file is used to control pre-tag checks.
# The filter on the right is invoked with the following arguments if no format strings are present:
#
# $1 -- tagname
# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
# $3 -- tagtype "?" on delete, "T" for branch, "N" for static
# $4 -- repository
# $5-> file revision [file revision ...]
#
# If any format strings are present in the filter, they will be replaced as follows:
# %b = branch mode = "?" (delete ops - unknown) | "T" (branch) | "N" (not branch)
# %o = operation = "add" | "mov" | "del"
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %t = tagname
# %{sVv} = attribute list = file name, old version tag will be deleted from,
# new version tag will be added to (or deleted from, but this feature is
# deprecated. When either old or new revision is unknown, doesn't exist,
# or isn't applicable, the string "NONE" will be placed on the command
# line.
#
# Note that %{sVv} is a list operator and not all elements are necessary. Thus %{sV} is
# a legal format string, but will only be replaced with file name and old revision.
# it also generates multiple arguments for each file being operated upon. i.e. if two
# files, file1 & file2, are having a tag moved from version 1.1 to versoin 1.1.2.9, %{sVv}
# will generate the following six arguments in this order: file1, 1.1, 1.1.2.9, file2, 1.1,
# 1.1.2.9.
#
# 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".
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/taginfo,v
Index: taginfo,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# The "taginfo" file is used to control pre-tag checks.
# The filter on the right is invoked with the following arguments if no format strings are present:
#
# $1 -- tagname
# $2 -- operation "add" for tag, "mov" for tag -F, and "del" for tag -d
# $3 -- tagtype "?" on delete, "T" for branch, "N" for static
# $4 -- repository
# $5-> file revision [file revision ...]
#
# If any format strings are present in the filter, they will be replaced as follows:
# %b = branch mode = "?" (delete ops - unknown) | "T" (branch) | "N" (not branch)
# %o = operation = "add" | "mov" | "del"
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %t = tagname
# %{sVv} = attribute list = file name, old version tag will be deleted from,
# new version tag will be added to (or deleted from, but this feature is
# deprecated. When either old or new revision is unknown, doesn't exist,
# or isn't applicable, the string "NONE" will be placed on the command
# line.
#
# Note that %{sVv} is a list operator and not all elements are necessary. Thus %{sV} is
# a legal format string, but will only be replaced with file name and old revision.
# it also generates multiple arguments for each file being operated upon. i.e. if two
# files, file1 & file2, are having a tag moved from version 1.1 to versoin 1.1.2.9, %{sVv}
# will generate the following six arguments in this order: file1, 1.1, 1.1.2.9, file2, 1.1,
# 1.1.2.9.
#
# 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".
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/val-tags
<<Binary file>>
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/verifymsg
Index: verifymsg
===================================================================
# 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.
#
# Format strings present in the filter will be replaced as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %l = name of log file to be verified.
#
# If no format strings are present in the filter, a default " %l" will
# be appended to the filter, but this usage is deprecated.
#
# 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.
1.1 maven-scm/scm-providers/cvslib/src/test/repository/CVSROOT/verifymsg,v
Index: verifymsg,v
===================================================================
head 1.1;
access ;
symbols ;
locks ; strict;
comment @# @;
1.1
date 2004.06.23.19.20.08; author trygvis; state Exp;
branches;
next ;
desc
@@
1.1
log
@initial checkin@
text
@# 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.
#
# Format strings present in the filter will be replaced as follows:
# %p = path relative to repository
# %r = repository (path portion of $CVSROOT)
# %l = name of log file to be verified.
#
# If no format strings are present in the filter, a default " %l" will
# be appended to the filter, but this usage is deprecated.
#
# 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.
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/test-repo/checkout/Foo.java,v
Index: Foo.java,v
===================================================================
head 1.1;
access;
symbols;
locks; strict;
comment @# @;
1.1
date 2003.11.23.19.51.25; author evenisse; state Exp;
branches;
next ;
desc
@@
1.1
log
@Some files for the cvs Checkout test command
@
text
@public class Foo
{
}
@
1.1 maven-scm/scm-providers/cvslib/src/test/repository/test-repo/checkout/Readme.txt,v
Index: Readme.txt,v
===================================================================
head 1.1;
access;
symbols;
locks; strict;
comment @# @;
1.1
date 2003.11.23.19.51.25; author evenisse; state Exp;
branches;
next ;
desc
@@
1.1
log
@Some files for the cvs Checkout test command
@
text
@This directory is for test the checkout command of generic-scm framework.
@