From owner-freebsd-stable@FreeBSD.ORG Mon Sep 11 00:13:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0099716A407 for ; Mon, 11 Sep 2006 00:13:50 +0000 (UTC) (envelope-from karl@FS.denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E599343D6E for ; Mon, 11 Sep 2006 00:13:46 +0000 (GMT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net (localhost [127.0.0.1]) by FS.denninger.net (8.13.6/8.13.1) with SMTP id k8B0DkD1045043 for ; Sun, 10 Sep 2006 19:13:46 -0500 (CDT) (envelope-from karl@FS.denninger.net) Received: from fs.denninger.net [127.0.0.1] by Spamblock-sys (LOCAL); Sun Sep 10 19:13:46 2006 Received: (from karl@localhost) by FS.denninger.net (8.13.6/8.13.1/Submit) id k8B0Dkr9045040 for freebsd-stable@freebsd.org; Sun, 10 Sep 2006 19:13:46 -0500 (CDT) (envelope-from karl) Date: Sun, 10 Sep 2006 19:13:46 -0500 From: Karl Denninger To: freebsd-stable@freebsd.org Message-ID: <20060911001346.GB44739@FS.denninger.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060909182831.GA32004@FS.denninger.net> <200609100159.k8A1xAIn089481@drugs.dv.isc.org> <20060910150526.GA31323@FS.denninger.net> <20060910151817.H8856@psg.com> <20060910181331.GA35166@FS.denninger.net> <20060910200554.J22428@saturn.araneidae.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060910200554.J22428@saturn.araneidae.co.uk> User-Agent: Mutt/1.4.2.1i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2006 00:13:50 -0000 On Sun, Sep 10, 2006 at 08:11:22PM +0000, Michael Abbott wrote: > >>You can track changes to a particular release - say by using > >>RELENG_6_1 rather than RELENG_6. In which case, would you still > >>say you are tracking STABLE? > >If I track RELENG_6 (once 6.0-RELEASE has gone out) then I'm by definition > >tracking -STABLE. > > Damn, I'm confused now. Let me try and get this straight: > > CURRENT > This is, by definition, broken a good part of the time, and is > what it says, namely current, ie work in progress. > > STABLE > This is broken some of the time and .. uh .. isn't really all that > stable, actually. > > RELENG_n_m > This is completely stable and only tracks security fixes. Incorrect. This is "completely FIXED", which is not the same thing as STABLE. "Fixed in a broken state" is still broken, aka the serial I/O problems in 6.x that I've found (and for which there is apparently no current fix in any of the branches of 6.x.) > RELENG_n (RELENG_6 at the moment) > Has somebody just said that RELENG_6 = STABLE? I'm going to guess > then that RELENG_7 is CURRENT. > No, this doesn't make sense to me at all. > > >Indeed, the current tag on my CVS tree is TRELENG_6! > > Eh? T? As in "Tag", which is the syntax that acutally shows up in the "CVS" directory under the source tree. -- -- Karl Denninger (karl@denninger.net) Internet Consultant & Kids Rights Activist http://www.denninger.net My home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.com Musings Of A Sentient Mind