From 507bd2a663ff8522df5206b65cb396e2a8b323a1 Mon Sep 17 00:00:00 2001 From: "N.N." Date: Fri, 14 Jun 2002 19:12:42 +0000 Subject: initial checkin svn path=/trunk/; revision=10 --- CVSROOT/editinfo | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 CVSROOT/editinfo (limited to 'CVSROOT/editinfo') diff --git a/CVSROOT/editinfo b/CVSROOT/editinfo new file mode 100644 index 00000000..d78886c1 --- /dev/null +++ b/CVSROOT/editinfo @@ -0,0 +1,21 @@ +# 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. +# +# 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. -- cgit v1.2.1