blob: 165345749f23fc72902ad74c6415fa0cb2da96f6 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
#
# $Id: editinfo,v 1.3 1996/02/07 14:35:37 peter Exp $
#
# The "editinfo" 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.
#
# Although these test could be handled by an interactive script being
# called via an entry in commitinfo, The information reported in
# such a script can't be easily merged into the report.
#
# 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.
#
# Note there is no "edit" example script currently available....
#
#DEFAULT $CVSROOT/CVSROOT/edit "%s"
# peter's edit post-processor.. (see verifymsg/logcheck now)
#DEFAULT $CVSROOT/CVSROOT/cvsedit
|
