| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20060728232654.GB2140@kroah.com> Date: Fri, 28 Jul 2006 16:26:54 -0700 From: Greg KH <greg@...ah.com> To: Nathan Scott <nathans@....com>, stable@...nel.org, Justin Piszcz <jpiszcz@...idpixels.com>, linux-kernel@...r.kernel.org Subject: Re: [stable] 2.6.17.[1-6] XFS Filesystem Corruption, Where is 2.6.17.7? On Tue, Jul 25, 2006 at 11:09:19PM +0200, Matthias Andree wrote: > On Tue, 25 Jul 2006, Matthias Andree wrote: > > > A serious suggestion is, providing that the arguments presented (people > > busy with OLS preparations and long review queue for 2.6.17.N+1): > > > > How about doing 2.6.17.7 as an interim release fixing just what is known > > to be critical at the point of the release, and then review the rest for > > 2.6.17.8? That would nicely fit the release early, release often - users > > like that particularly for bug fixes. > > OK, 2.6.17.7 is out, but still - is this suggestion worthwhile > considering for future -stable release engineering or just crap? .7 took a bit longer than expected, due to some security bugs that needed to be added to the queue, combined with the fact that both Chris and I were busy with OLS stuff. Normally we both aren't travelling at the same time, but right then, we were, so we couldn't respond as quickly as it seems some people felt we should have. Sorry about this, we'll try to do better next time. greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists