diff options
| author | root <root@208e9e7b-5314-0410-a742-e7e81cd9613c> | 2005-05-19 19:12:41 +0000 |
|---|---|---|
| committer | root <root@208e9e7b-5314-0410-a742-e7e81cd9613c> | 2005-05-19 19:12:41 +0000 |
| commit | c0271260cf77ea47bd589e6fc0a2699a9a1dae98 (patch) | |
| tree | 78bc12b4b986b50e59a5a4be94b58195261acb2e /CVSROOT/verifymsg | |
| parent | 77e758361bbfd93a176fa58f075f5505aa8dcc3b (diff) | |
initial checkin
git-svn-id: https://svn.roundcube.net/trunk@2 208e9e7b-5314-0410-a742-e7e81cd9613c
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 000000000..86f747ce2 --- /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. |
