From 0ea5fc66924303d1bf73ba283a383e2aadee02f2 Mon Sep 17 00:00:00 2001 From: neodarz Date: Sat, 11 Aug 2018 20:21:34 +0200 Subject: Initial commit --- .../plain&only_with_tag=HEAD/index.html | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 cvs/cvsweb.cgi/~checkout~/CVSROOT/editinfo?rev=1.1&content-type=text/plain&only_with_tag=HEAD/index.html (limited to 'cvs/cvsweb.cgi/~checkout~/CVSROOT/editinfo?rev=1.1&content-type=text') diff --git a/cvs/cvsweb.cgi/~checkout~/CVSROOT/editinfo?rev=1.1&content-type=text/plain&only_with_tag=HEAD/index.html b/cvs/cvsweb.cgi/~checkout~/CVSROOT/editinfo?rev=1.1&content-type=text/plain&only_with_tag=HEAD/index.html new file mode 100644 index 00000000..d78886c1 --- /dev/null +++ b/cvs/cvsweb.cgi/~checkout~/CVSROOT/editinfo?rev=1.1&content-type=text/plain&only_with_tag=HEAD/index.html @@ -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