From owner-freebsd-stable Mon Apr 9 17:44:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id 6BEFE37B422 for ; Mon, 9 Apr 2001 17:44:54 -0700 (PDT) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.11.3/8.11.3) id f3A0oFr01253; Mon, 9 Apr 2001 19:50:15 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.7 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 09 Apr 2001 19:50:15 -0500 (CDT) Organization: @Home Network From: Conrad Sabatier To: Bob K Subject: Re: supfile idea (was Re: Releases) Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Apr-2001 Bob K wrote: > On Mon, 9 Apr 2001, Mike Meyer wrote: > > [snip] >> Matthew Emmerton types: >> > In the case of people running -CURRENT on a production machine, that's >> > just >> > a plain and simple mistake. Ever wonder how someone who barely knows how >> > to >> > use cvsup and make world manages to obtain -CURRENT in the first place? >> >> No, because it happens to everyone who uses the standard-supfile in >> the /usr/share/examples/cvsup. I think that stable-supfile should >> vanish from that directory, and standard-supfile should be right for >> the branch the system came from, no matter which branch that was. > [snip] > > I'm not going to touch on the rest of the thread, but that idea seems like > an extremely good one. How 'bout putting this in once 4.3's gone out the > door? I think it might be better, perhaps, to rename standard-supfile to something like unstable-supfile (unstable-supfile-use-at-your-own-risk? :-), and leave stable-supfile alone. That should be enough to ward off the wary. -- Conrad Sabatier conrads@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message