From owner-freebsd-hackers  Mon Apr  7 01:19:46 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA00371
          for hackers-outgoing; Mon, 7 Apr 1997 01:19:46 -0700 (PDT)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA00363
          for <hackers@freebsd.org>; Mon, 7 Apr 1997 01:19:40 -0700 (PDT)
Message-Id: <199704070819.BAA00363@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA290950838; Mon, 7 Apr 1997 18:13:58 +1000
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: on the subject of changes to -RELEASEs...
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Mon, 7 Apr 1997 18:13:58 +1000 (EST)
Cc: hackers@freebsd.org
In-Reply-To: <199704070735.RAA05938@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Apr 7, 97 05:05:19 pm
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In some mail from Michael Smith, sie said:
> Darren Reed stands accused of saying:
> > I've noticed some commits recently for RELENG_2_2 and as other have
> > commented, this changes (totally) a set of files for 2.2.1.
> 
> No, it changes files for 2.2-stable.  2.2.1 is history; you are watching
> the normal progression towards the next 2.2.x release.

okay, I think I understand the labels so far:
        RELENG_2_2_1_RELEASE:1.7
        RELENG_2_2_0_RELEASE:1.7
        RELENG_2_2:1.7.0.2

and RELENG_2_2 is actually "2.2-STABLE".  Yes, previously I'd never
noticed the other RELENG_2_2_* tags and was confusing things.

> Yeah, right.  Don't get me started there 8) Just to observe that
> having a set of diffs against "something" is nothing compared to
> having a local copy of the entire CVS repository for the subsystem in
> question.

What if I don't want an entire CVS repository ?

> And configuring CVSup is _simple_ and _painless_ and it is the
> greatest joy of any software I have ever met in regard to source
> tracking.

Why do I need CVSup ?  What if I don't want to allow CVS through my
firewall (or sup for that matter) ?  (at this point, CVSup implies
maintaining a CVS tree as well as a src tree to compile from).

Sure, CVS might be superior to using diffs, BUT, big BUT here, using CVS
will require TWICE the space to store the source.

Maybe I bought FreeBSD 2.2 on CD-ROM, I want to upgrade to 2.2.1.
Alternatives currently are:
* buy the new CD when it becomes available
* download all the binaries
* download all the source
* setup cvsup

IMHP, this is not exactly "user friendly".

Darren