From owner-freebsd-stable@FreeBSD.ORG  Sun Sep 10 20:11:26 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 9B2B416A40F
	for <freebsd-stable@freebsd.org>; Sun, 10 Sep 2006 20:11:26 +0000 (UTC)
	(envelope-from michael@araneidae.co.uk)
Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CCDBC43D5A
	for <freebsd-stable@freebsd.org>; Sun, 10 Sep 2006 20:11:23 +0000 (GMT)
	(envelope-from michael@araneidae.co.uk)
Received: from saturn.araneidae.co.uk (localhost [127.0.0.1])
	by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k8AKBMYa022445
	for <freebsd-stable@freebsd.org>; Sun, 10 Sep 2006 20:11:22 GMT
	(envelope-from michael@araneidae.co.uk)
Received: from localhost (michael@localhost)
	by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id
	k8AKBMd8022442
	for <freebsd-stable@freebsd.org>; Sun, 10 Sep 2006 20:11:22 GMT
	(envelope-from michael@araneidae.co.uk)
X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing
	-bs
Date: Sun, 10 Sep 2006 20:11:22 +0000 (GMT)
From: Michael Abbott <michael@araneidae.co.uk>
To: freebsd-stable@freebsd.org
In-Reply-To: <20060910181331.GA35166@FS.denninger.net>
Message-ID: <20060910200554.J22428@saturn.araneidae.co.uk>
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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Sep 2006 20:11:26 -0000

>> 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.

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?