From owner-freebsd-commit  Wed Sep 13 01:01:59 1995
Return-Path: commit-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA12168
          for freebsd-commit-outgoing; Wed, 13 Sep 1995 01:01:59 -0700
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA12153
          for cvs-all-outgoing; Wed, 13 Sep 1995 01:01:42 -0700
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA12140
          for cvs-usrbin-outgoing; Wed, 13 Sep 1995 01:01:40 -0700
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA12127
          ; Wed, 13 Sep 1995 01:01:11 -0700
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA04951; Wed, 13 Sep 1995 01:00:06 -0700
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199509130800.BAA04951@GndRsh.aac.dev.com>
Subject: Re: cvs commit: src/usr.bin/find function.c
To: nate@rocky.sri.MT.net (Nate Williams)
Date: Wed, 13 Sep 1995 01:00:06 -0700 (PDT)
Cc: peter@jhome.dialix.com, nate@rocky.sri.MT.net,
        CVS-commiters@freefall.freebsd.org, cvs-usrbin@freefall.freebsd.org
In-Reply-To: <199509130408.WAA08549@rocky.sri.MT.net> from "Nate Williams" at Sep 12, 95 10:08:31 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1926      
Sender: commit-owner@FreeBSD.org
Precedence: bulk

> 
> [ Direct CVS repository munging ]
> > > > Whip me, beat me, call me bad names, but don't take away my CVS
> > > > privileges. :)
> > 
> > Per mail to this list these types of actions can lead to, and well
> > if they cause the repository manager heartache, loss of commit privlidge.
> 
> Of course, but if a person knows what they are doing (or at least if
> they can fake it) it avoids the heartache and grief.

No, it has been simply stated on at least 3 occasions ``cvs admin'' is
to be used _ONLY_ by repository managers.  There is no reason for you
to use this, and as Peter explains you could really screw someone over,
or infact the repository itself by your actions.

> 
> > I will also presume that he knows that I can now find his commit in
> > the commitlogs but can not find it in the RCS files :-(.
> 
> Yes, but it's *very* obvious what happened, since the next commit
> message in the log is the fix which was mentioned in the previous (no
> longer necessary) commitlog messages.

It is not obvious what happened when trying to look at this 6 months
from now and understand the descrepancy between the cvs commitlog files
and the rcs loginfo for the file.  The mail thread is no place near
that stuff.

> > Along with the fact some one could have supped 1.5, burned it on a
> > cdrom and now what is 1.5 is a different file :-(.
> 
> If someone was silly enough to burn a CD-ROM of the tree in it's current
> state, *AND* if they could get the sup to happen after my two original
> commits but before the third, they deserved to get burned.

NO, it is just plain stupid for you to have done this, please do not
due it again.  A commit would have done the job, not involved any
possible race conditions and clearly docuemented the sequence of events.


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD