diff options
author | N.N. <root@users.sourceforge.net> | 2002-06-14 19:12:42 +0000 |
---|---|---|
committer | N.N. <root@users.sourceforge.net> | 2002-06-14 19:12:42 +0000 |
commit | 507bd2a663ff8522df5206b65cb396e2a8b323a1 (patch) | |
tree | 7809f743889a06de428b65ce5216ea9686df204a /CVSROOT/verifymsg |
initial checkinsvn2git-root
svn path=/trunk/; revision=10
Diffstat (limited to 'CVSROOT/verifymsg')
-rw-r--r-- | CVSROOT/verifymsg | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/CVSROOT/verifymsg b/CVSROOT/verifymsg new file mode 100644 index 00000000..86f747ce --- /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. |