summaryrefslogtreecommitdiff
path: root/CVSROOT/editinfo
diff options
context:
space:
mode:
authoriovar <iovar@f606c939-3180-4ac9-a4b8-4b8779d57d0a>2008-09-10 17:37:06 +0000
committeriovar <iovar@f606c939-3180-4ac9-a4b8-4b8779d57d0a>2008-09-10 17:37:06 +0000
commitfbcba8aa5e4e9dd3eab5d0c508b8dfcd3cd3ad5f (patch)
tree168992fa960047c42339ede2402e896d773d8b2a /CVSROOT/editinfo
parent9b080cbfbabc23a216277f658c2d009fdead6f93 (diff)
removed migration leftovers (CVSROOT directory and everything beneath it)
git-svn-id: https://recordmydesktop.svn.sourceforge.net/svnroot/recordmydesktop/trunk@503 f606c939-3180-4ac9-a4b8-4b8779d57d0a
Diffstat (limited to 'CVSROOT/editinfo')
-rw-r--r--CVSROOT/editinfo21
1 files changed, 0 insertions, 21 deletions
diff --git a/CVSROOT/editinfo b/CVSROOT/editinfo
deleted file mode 100644
index d78886c..0000000
--- a/CVSROOT/editinfo
+++ /dev/null
@@ -1,21 +0,0 @@
-# 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.
© All Rights Reserved