From owner-freebsd-current  Wed Sep  4 13:38:13 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA01409
          for current-outgoing; Wed, 4 Sep 1996 13:38:13 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA01403
          for <current@freebsd.org>; Wed, 4 Sep 1996 13:38:06 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA07326; Wed, 4 Sep 1996 13:36:01 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199609042036.NAA07326@phaeton.artisoft.com>
Subject: Re: Latest Current build failure
To: nate@mt.sri.com (Nate Williams)
Date: Wed, 4 Sep 1996 13:36:01 -0700 (MST)
Cc: terry@lambert.org, nate@mt.sri.com, current@freebsd.org
In-Reply-To: <199609041858.MAA01487@rocky.mt.sri.com> from "Nate Williams" at Sep 4, 96 12:58:29 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > It solves a problem in the suggested replacement for the existing system.
> 
> No, it doesn't.  As has been discussed to death in the past, it solves
> *NO* problems in the past or present that can be solved.  The *problem*
> is a human problem that can't be solved adequately using a computer.  It
> needs human intervention (ala. Jordan's cookies).  No 'locking' protocol
> within CVS will solve the problem, as the problem exists outside the
> scope of the version control software.
> 
> 'Nuff said, you can continue to waste both my time and others, but it
> will be ignored.

	while( cookie not present)
		continue;

Looks like a damn lock to me.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.