From 68c983fca8336e31e52b872b540a67604c1b26a3 Mon Sep 17 00:00:00 2001
From: root
Date: Fri, 11 Mar 2005 18:11:30 +0000
Subject: initial checkin

---
 CVSROOT/verifymsg | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 CVSROOT/verifymsg

(limited to 'CVSROOT/verifymsg')

diff --git a/CVSROOT/verifymsg b/CVSROOT/verifymsg
new file mode 100644
index 0000000..86f747c
--- /dev/null
+++ b/CVSROOT/verifymsg
@@ -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.
-- 
cgit v1.1