summaryrefslogtreecommitdiff
path: root/CVSROOT/verifymsg
diff options
context:
space:
mode:
authornobody <nobody@f19166aa-fa4f-0410-85c2-fa1106f25c8a>2003-11-06 22:17:22 +0000
committernobody <nobody@f19166aa-fa4f-0410-85c2-fa1106f25c8a>2003-11-06 22:17:22 +0000
commit762c403822a22603bc4bbf640830feb8b9416549 (patch)
tree0b09a8ed2e86a25dc9144c2142c3759ce46129b8 /CVSROOT/verifymsg
parent5600e7c933126feb6a410aa37cc5701803983edb (diff)
downloadpyserial-git-762c403822a22603bc4bbf640830feb8b9416549.tar.gz
This commit was manufactured by cvs2svn to create tag 'release2_0'.release2_0
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 @@
-# 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.