head	1.1;
access;
symbols
	libdrm-1_0_4:1.1
	trunk-20021125:1.1
	mesa-4-1-branch:1.1.0.12
	mesa-3-5-branch:1.1.0.10
	tdfx-2-0-branch:1.1.0.8
	tdfx-2-0-trunk:1.1
	dispatch-0-0-3-20000225-merge:1.1
	dispatch-0-0-3-branch:1.1.0.6
	dispatch-0-0-2-branch:1.1.0.4
	dispatch-0-0-1-20000129-merge:1.1
	dispatch-0-0-1-branch:1.1.0.2;
locks; strict;
comment	@# @;


1.1
date	99.11.24.02.05.03;	author root;	state Exp;
branches;
next	;


desc
@@



1.1
log
@initial checkin@
text
@# 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.
@