1head 1.1; 2access ; 3symbols ; 4locks ; strict; 5comment @# @; 6 7 81.1 9date 2008.09.04.16.09.17; author austvik; state Exp; 10branches; 11next ; 12commitid 3XIAdD8FSh3Pitht; 13 14desc 15@@ 16 17 18 191.1 20log 21@initial checkin@ 22text 23@# The "verifymsg" file is used to allow verification of logging 24# information. It works best when a template (as specified in the 25# rcsinfo file) is provided for the logging procedure. Given a 26# template with locations for, a bug-id number, a list of people who 27# reviewed the code before it can be checked in, and an external 28# process to catalog the differences that were code reviewed, the 29# following test can be applied to the code: 30# 31# Making sure that the entered bug-id number is correct. 32# Validating that the code that was reviewed is indeed the code being 33# checked in (using the bug-id number or a seperate review 34# number to identify this particular code set.). 35# 36# If any of the above test failed, then the commit would be aborted. 37# 38# Format strings present in the filter will be replaced as follows: 39# %c = canonical name of the command being executed 40# %R = the name of the referrer, if any, otherwise the value NONE 41# %p = path relative to repository 42# %r = repository (path portion of $CVSROOT) 43# %l = name of log file to be verified. 44# 45# If no format strings are present in the filter, a default " %l" will 46# be appended to the filter, but this usage is deprecated. 47# 48# Actions such as mailing a copy of the report to each reviewer are 49# better handled by an entry in the loginfo file. 50# 51# One thing that should be noted is the the ALL keyword is not 52# supported. There can be only one entry that matches a given 53# repository. 54@ 55 56