From owner-freebsd-current Sun Mar 17 8:51:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 3D4F137B41A; Sun, 17 Mar 2002 08:51:12 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2HGpBlv011069; Sun, 17 Mar 2002 08:51:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2HGnvNm011052; Sun, 17 Mar 2002 08:49:57 -0800 (PST) Date: Sun, 17 Mar 2002 08:49:57 -0800 From: "David O'Brien" To: Terry Lambert Cc: re@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: -CURRENT Feature Slush is OVER Message-ID: <20020317084957.D10393@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <20020316111818.GO17499@freebsdmall.com> <1016289691.91096.2.camel@notebook> <20020316115309.E95652@dragon.nuxi.com> <3C93C273.8356D01@mindspring.com> <20020317002235.B3875@dragon.nuxi.com> <3C945A4A.3FC77CB1@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C945A4A.3FC77CB1@mindspring.com>; from tlambert2@mindspring.com on Sun, Mar 17, 2002 at 12:56:42AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Mar 17, 2002 at 12:56:42AM -0800, Terry Lambert wrote: > It seems to me that, at worst, this is being done to "prove > to the heathens" that use of Perforce is a bad idea. It > certainly is, if history is going to be lost, but that's not > a result of the tool, here, it's a result of intention. > > At best, Perforce is being used because the release engineers > have less power over branching in the CVS repository than the > core team *should* be loaning them. So you would like to screw the project just out of principle? I know you know enough about CVS to know the limitations that laying down this tag would have on the ability to do repository surgery. > Either way, it's bad news when it won't be possible to > reproduce an official code cut -- even if it's not a > release -- from the repository. > > What is a repository good for, if you can't recover your > history from it? The way Linux is developed, they release > code that's not recoverable from a repository, ony from > the release materials themselves. They have no repository > because they *intentionally* have no perception of history. Thanks for your input. If this will be the result of DP snapshots, you've now convinced me to strongly object to them. I had reservations about us doing such an "official" snapshot and the impact it has on the CVS repo and developer code slush restrictions. Next time I will voice them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message