summaryrefslogtreecommitdiff
path: root/CVSROOT/verifymsg
diff options
context:
space:
mode:
authorImre Kaloz <kaloz@openwrt.org>2005-10-17 12:24:08 +0000
committerImre Kaloz <kaloz@openwrt.org>2005-10-17 12:24:08 +0000
commit15bee86fc3df92f0bbdf0a17eac3915965983396 (patch)
tree6a621c91d22f093f023a29c72252ea47ba9fb32a /CVSROOT/verifymsg
parent487c71693d31836144cd0a55ae73b76c64f71561 (diff)
downloadmtk-20170518-15bee86fc3df92f0bbdf0a17eac3915965983396.zip
mtk-20170518-15bee86fc3df92f0bbdf0a17eac3915965983396.tar.gz
mtk-20170518-15bee86fc3df92f0bbdf0a17eac3915965983396.tar.bz2
removed the old directories, too.. cleanup is ready, yay
SVN-Revision: 2130
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.