[evolvis-commits] r9208: initial checkin

mirabilos at evolvis.org mirabilos at evolvis.org
Thu Feb 24 17:20:42 CET 2011


Author: mirabilos
Date: 2011-02-24 17:20:41 +0100 (Thu, 24 Feb 2011)
New Revision: 9208

Added:
   trunk/gforge_base/evolvisforge-5.1/CVSROOT/editinfo
   trunk/gforge_base/evolvisforge-5.1/CVSROOT/modules
   trunk/gforge_base/evolvisforge-5.1/CVSROOT/notify
   trunk/gforge_base/evolvisforge-5.1/CVSROOT/rcsinfo
   trunk/gforge_base/evolvisforge-5.1/CVSROOT/taginfo
   trunk/gforge_base/evolvisforge-5.1/CVSROOT/verifymsg
Log:
initial checkin

Added: trunk/gforge_base/evolvisforge-5.1/CVSROOT/editinfo
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/CVSROOT/editinfo	                        (rev 0)
+++ trunk/gforge_base/evolvisforge-5.1/CVSROOT/editinfo	2011-02-24 16:20:41 UTC (rev 9208)
@@ -0,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.

Added: trunk/gforge_base/evolvisforge-5.1/CVSROOT/modules
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/CVSROOT/modules	                        (rev 0)
+++ trunk/gforge_base/evolvisforge-5.1/CVSROOT/modules	2011-02-24 16:20:41 UTC (rev 9208)
@@ -0,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.

Added: trunk/gforge_base/evolvisforge-5.1/CVSROOT/notify
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/CVSROOT/notify	                        (rev 0)
+++ trunk/gforge_base/evolvisforge-5.1/CVSROOT/notify	2011-02-24 16:20:41 UTC (rev 9208)
@@ -0,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"

Added: trunk/gforge_base/evolvisforge-5.1/CVSROOT/rcsinfo
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/CVSROOT/rcsinfo	                        (rev 0)
+++ trunk/gforge_base/evolvisforge-5.1/CVSROOT/rcsinfo	2011-02-24 16:20:41 UTC (rev 9208)
@@ -0,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".

Added: trunk/gforge_base/evolvisforge-5.1/CVSROOT/taginfo
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/CVSROOT/taginfo	                        (rev 0)
+++ trunk/gforge_base/evolvisforge-5.1/CVSROOT/taginfo	2011-02-24 16:20:41 UTC (rev 9208)
@@ -0,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".

Added: trunk/gforge_base/evolvisforge-5.1/CVSROOT/verifymsg
===================================================================
--- trunk/gforge_base/evolvisforge-5.1/CVSROOT/verifymsg	                        (rev 0)
+++ trunk/gforge_base/evolvisforge-5.1/CVSROOT/verifymsg	2011-02-24 16:20:41 UTC (rev 9208)
@@ -0,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.



More information about the evolvis-commits mailing list