head	1.8;
access;
symbols
	newcvs:1.1.1.1
	NEWCVS:1.1.1;
locks; strict;
comment	@# @;


1.8
date	2001.08.30.21.32.19;	author joe;	state Exp;
branches;
next	1.7;

1.7
date	2000.08.28.11.30.55;	author joe;	state Exp;
branches;
next	1.6;

1.6
date	2000.02.13.04.04.28;	author peter;	state Exp;
branches;
next	1.5;

1.5
date	99.08.27.22.46.56;	author peter;	state Exp;
branches;
next	1.4;

1.4
date	97.06.08.17.02.34;	author peter;	state Exp;
branches;
next	1.3;

1.3
date	96.02.07.14.35.37;	author peter;	state Exp;
branches;
next	1.2;

1.2
date	95.08.20.23.23.38;	author peter;	state Exp;
branches;
next	1.1;

1.1
date	94.05.24.08.59.42;	author rgrimes;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	94.05.24.08.59.43;	author rgrimes;	state Exp;
branches;
next	1.1.1.2;

1.1.1.2
date	95.03.28.06.48.50;	author pst;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	95.03.28.07.58.55;	author pst;	state Exp;
branches;
next	;


desc
@@


1.8
log
@Update with the changes introduced with the recent upgrade of CVS.
@
text
@#
# $FreeBSD: CVSROOT/editinfo,v 1.7 2000/08/28 11:30:55 joe 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.
#
# 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"
@


1.7
log
@Sychronise with the default versions that CVS (1.10.7) creates in
a new repository.

This commit only affects comments.
@
text
@d2 1
a2 1
# $FreeBSD: CVSROOT/editinfo,v 1.6 2000/02/13 04:04:28 peter Exp $
d22 2
a23 2
# One thing that should be noted  is the the ALL keyword is not
# supported. There can be only one entry that matches a given
@


1.6
log
@Update the commit scripts to understand 'Approved by:' and kill cvsedit.
@
text
@d2 1
a2 1
# $FreeBSD: CVSROOT/editinfo,v 1.5 1999/08/27 22:46:56 peter Exp $
a20 4
#
# 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.
@


1.5
log
@$Id$ -> $FreeBSD$
@
text
@d2 1
a2 1
# $FreeBSD$
a32 2
# peter's edit post-processor.. (see verifymsg/logcheck now)
#DEFAULT			$CVSROOT/CVSROOT/cvsedit
@


1.4
log
@Deactivate the cvsedit wrapper around $EDITOR, verifymsg/logcheck should
be doing a better job now.  (fingers crossed)
@
text
@d2 1
a2 1
# $Id: editinfo,v 1.3 1996/02/07 14:35:37 peter Exp $
@


1.3
log
@Attempt to fix some outstanding bugs/misfeatures/bogons in the CVSROOT
code, as well as simplifying some admin procedures.

The main change is to stop multi-directory commits only having the subject
info of the last directory, and not being sent to all the lists, and not
being logged to the appropriate commitlogs.

updateCVSROOT is gone (yay!), it's functionality is replaced by a cvs-1.6
feature - the 'checkoutlist' file, which is designed explicitly for this.
This will stop the easy-import users from getting told the mailing list
is out of date when a committer has been added but had missed out on being
put on the cvs-committers mailing list.

Update the comments and info in the *info files with the cvs-1.6 headers,
this fixes a few typos, clarifys some things, corrects some misleading
comments, etc.

Some stub files added to indicate how new cvs-1.6+ functionality is used,
but left commented out (taginfo, cvswrappers, etc)

All hard-coded references to /home/ncvs are changed back to $CVSROOT
(as suggested to me by bde) now that cvs-1.6+ makes a special effort
to ensure $CVSROOT is always set.  This allows the $CVSROOT files to be
used elsewhere (eg: for testing) with much less pain.

mkavail is history as well, it was often being forgotten.  cvs-committers
now takes the user list from /etc/group:ncvs via a trivial perl script.
This is so that we still have the ability to temporarily disable commit
access via 'avail' without cutting off the cvs-committers mailing list.
Since /etc/group editing is still required, this is not a new admin
overhead.  If we ever change so that membership of "ncvs" is not required
(eg: /usr/bin/cvs becomes setgid and access control is via avail) then
we are going to have to do it some other way.  (I have ideas)

I have tested this on my machines, but it is possible that I have missed
something.  As usual, please yell if I've botched it.
@
text
@d2 1
a2 1
# $Id$
d33 2
a34 2
# peter's edit post-processor..
DEFAULT			$CVSROOT/CVSROOT/cvsedit
@


1.2
log
@Insert hook to call CVSROOT/cvsedit..
This hook is launched by cvs instead of your editor when commiting.
cvsedit runs the editor for you, and does some post-processing on the
file after you quit..  It does the following:
- Remove trailing whitespace
- Collapse multiple blank lines
- Removes empty "Reviewed-by" etc lines, stopping cvs from putting them
  into the rcs log.
- Removes leading and trailing blank lines..
- maintains the file timestamps if no changes are made, allowing you to
  abort a commit properly.
(Sadly, I didn't have time to get the AI code running that was meant to
 check your code for you and find any bugs in your committed code.. :-)

Reviewed by:	Rod Grimes
@
text
@d2 1
a2 2
# editinfo,v 1.1 1992/03/21 06:49:39 berliner Exp
# $FreeBSD$
d30 1
a30 1
#DEFAULT			$CVSROOT/CVSROOT/edit
d32 1
a32 2
# uncomment this to deal with the new edit hook
#DEFAULT			/home/ncvs/CVSROOT/new_edithook
d34 1
a34 1
DEFAULT			/home/ncvs/CVSROOT/cvsedit
@


1.1
log
@Initial revision
@
text
@d31 6
a36 1
#DEFAULT			$CVSROOT/CVSROOT/edit "%s"
@


1.1.1.1
log
@Initial CVSROOT setup
@
text
@@


1.1.1.2
log
@add new edit hook test
@
text
@a31 1
pst-test			$CVSROOT/CVSROOT/new_edithook "%s"
@


1.1.1.3
log
@add comment for new edit hook
@
text
@d31 2
a32 4
#DEFAULT			$CVSROOT/CVSROOT/edit
#
# uncomment this to deal with the new edit hook
#DEFAULT			/home/ncvs/CVSROOT/new_edithook
@
