From owner-freebsd-current  Wed Sep  4 11:20:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA25029
          for current-outgoing; Wed, 4 Sep 1996 11:20:30 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA25023;
          Wed, 4 Sep 1996 11:20:28 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by who.cdrom.com (8.7.5/8.6.11) with SMTP id LAA17516
          ; Wed, 4 Sep 1996 11:18:51 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA06901; Wed, 4 Sep 1996 11:14:31 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199609041814.LAA06901@phaeton.artisoft.com>
Subject: Re: Latest Current build failure
To: jhs@FreeBSD.org
Date: Wed, 4 Sep 1996 11:14:31 -0700 (MST)
Cc: sja@tekla.fi, current@FreeBSD.org
In-Reply-To: <199609040849.KAA00828@vector.jhs.no_domain> from "Julian H. Stacey" at Sep 4, 96 10:49:11 am
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

> Hi, Reference:
> > From: sja@tekla.fi (Sakari Jalovaara) 
> > Subject: Re: Latest Current build failure 
> > Date: Tue, 3 Sep 1996 11:27:34 +0300 
> > Message-id: <9609030827.AA05232@tahma.tekla.fi> 
> >
> > How about this idea:
> > 
> > Everyone cvsups the bleeding edge RCS files.
> 
> NO !	That assumes everyone has good net connectivity ... & they don't all.
> CTM has distinct advantages for maintenance of my local CVS tree,
> namely, only my local ISP needs be up to supply the mail,
> even if the rest of the net, or freebsd servers are dead or slow as hell... 
> no problem !

You are missing the forest for the trees.

Please replace "cvsups" with "somehow obtains".  The point of the
suggestion was to externalize the "it's good" token from the tree
representation.

Other than adding that I'd like to see the "it's good" token checked into
the tree somewhere as well so there is an "it's good" history (the token
approach relies on the idea that the tree itself does not have to be
kept "good"), I have to agree that this is a workable, if suboptimal,
fix for the problem.


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