Date: Sun, 10 Sep 2006 20:11:22 +0000 (GMT) From: Michael Abbott <michael@araneidae.co.uk> To: freebsd-stable@freebsd.org Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Message-ID: <20060910200554.J22428@saturn.araneidae.co.uk> In-Reply-To: <20060910181331.GA35166@FS.denninger.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060910200554.J22428>