Date: Sun, 10 Sep 2006 22:15:20 +0300 From: "Reko Turja" <reko.turja@liukuma.net> To: <freebsd-stable@freebsd.org> Subject: Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?! Message-ID: <00c301c6d50d$751ffe80$0a0aa8c0@rivendell> 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><20060910183631.GA6406@xor.obsecurity.org> <20060910183958.GA35701@FS.denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Karl Denninger" <karl@denninger.net> To: <freebsd-stable@freebsd.org> Sent: Sunday, September 10, 2006 9:39 PM > Yes it is, in the general case; in any event if you track RELENG_6_1 > you will > get no bug fixes in general - security related items to filter back > down but > in general bug reports posted against a -RELEASE are, if addressed, > put into > -STABLE. You would like untested fixes to hit the release version first? By the way, possible breakage of STABLE due MFC process was announced a good while ago... -Reko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00c301c6d50d$751ffe80$0a0aa8c0>