From 8a632fe2dff10b26c7b8465efc71f1d0c2beb36a Mon Sep 17 00:00:00 2001 From: Guido Kanschat Date: Mon, 24 Nov 1997 13:02:38 +0000 Subject: [PATCH] initial checkin of editinfo git-svn-id: https://svn.dealii.org/trunk@2 0785d39b-7218-0410-832d-ea1e28bc413d --- CVSROOT/editinfo | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 CVSROOT/editinfo diff --git a/CVSROOT/editinfo b/CVSROOT/editinfo new file mode 100644 index 0000000000..d78886c152 --- /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. -- 2.39.5