summaryrefslogtreecommitdiff
path: root/CVSROOT/verifymsg
diff options
context:
space:
mode:
authorBjörn Stenberg <bjorn@haxx.se>2002-01-17 16:11:26 +0000
committerBjörn Stenberg <bjorn@haxx.se>2002-01-17 16:11:26 +0000
commit2daf14965c39bc911793520a90027797ad92df74 (patch)
tree8e83c67f2b86e7f0823f4fc3273ff65a081bb8c1 /CVSROOT/verifymsg
parente196759fbd5142d1197320f62b33022f3b80ef98 (diff)
downloadrockbox-2daf14965c39bc911793520a90027797ad92df74.tar.gz
rockbox-2daf14965c39bc911793520a90027797ad92df74.zip
initial checkin
git-svn-id: svn://svn.rockbox.org/rockbox/trunk@3 a1c6a512-1295-4272-9138-f99709370657
Diffstat (limited to 'CVSROOT/verifymsg')
-rw-r--r--CVSROOT/verifymsg21
1 files changed, 21 insertions, 0 deletions
diff --git a/CVSROOT/verifymsg b/CVSROOT/verifymsg
new file mode 100644
index 0000000000..86f747ce22
--- /dev/null
+++ b/CVSROOT/verifymsg
@@ -0,0 +1,21 @@
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.