summaryrefslogtreecommitdiffstats
path: root/CVSROOT/verifymsg
diff options
context:
space:
mode:
authorcvs2git2005-03-12 13:06:31 +0000
committercvs2git2005-03-12 13:06:31 +0000
commitf2e953207e43b606f16dcd350aa1bb0b80c5883b (patch)
treec781d64801cce3249c0301a7354dcf7150bc5a00 /CVSROOT/verifymsg
parentInitial import (diff)
downloadurunlevel-start.zip
urunlevel-start.tar.gz
urunlevel-start.tar.bz2
urunlevel-start.tar.xz
This commit was manufactured by cvs2svn to create tag 'start'.start
Diffstat (limited to 'CVSROOT/verifymsg')
-rw-r--r--CVSROOT/verifymsg21
1 files changed, 0 insertions, 21 deletions
diff --git a/CVSROOT/verifymsg b/CVSROOT/verifymsg
deleted file mode 100644
index 86f747c..0000000
--- a/CVSROOT/verifymsg
+++ /dev/null
@@ -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.