From owner-freebsd-current@FreeBSD.ORG  Wed Aug 18 19:26:44 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id F2DE816A4CE; Wed, 18 Aug 2004 19:26:43 +0000 (GMT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id D441143D1F; Wed, 18 Aug 2004 19:26:43 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 8636F148D7; Wed, 18 Aug 2004 14:26:43 -0500 (CDT)
Date: Wed, 18 Aug 2004 14:26:43 -0500 (CDT)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Robert Watson <rwatson@freebsd.org>
In-Reply-To: <Pine.NEB.3.96L.1040818110443.55952A-100000@fledge.watson.org>
Message-ID: <Pine.LNX.4.44.0408181420070.19515-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Thu, 19 Aug 2004 12:03:43 +0000
cc: drhodus@machdep.com
cc: current@freebsd.org
Subject: Re: Public Access to Perforce?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Aug 2004 19:26:44 -0000

On Wed, 18 Aug 2004, Robert Watson wrote:

> One of our hopes was to find a model that has some of the benefits of a
> "contrib" model, wherein only more stable/discrete change sets go into
> CVS, but without the more painful aspects of CVS vendor branches or the
> notion of the "primary" copy being maintained elsewhere.

Don't forget the fact that anyone who tracks our CVS trees via cvsup also
winds up with a copy of all that history, forever, on their hard drive.
If the 'history' were to expand to cover all the intermediate and
rejected steps in some of these sub-projects, we would add repo bloat
(and resulting server and download times) for very little gain.

Just because something gets merged into -current doesn't mean that
the changes have to stand, either: there is plenty of evidence that
things get critically reviewed and revised, no matter what the source.

mcl