| 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: <46389BBF.5000508@redhat.com> Date: Wed, 02 May 2007 10:10:07 -0400 From: Chuck Ebbert <cebbert@...hat.com> To: Chris Wright <chrisw@...s-sol.org> CC: Greg KH <greg@...ah.com>, Alan Cox <alan@...rguk.ukuu.org.uk>, Jeff Garzik <jeff@...zik.org>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, stable@...nel.org Subject: Re: [stable] to something appropriate (was Re: 2.6.22 -mm merge plans) Chris Wright wrote: > * Greg KH (greg@...ah.com) wrote: >> And is this really a problem? The whole goal of the -stable tree was to >> accomidate the users who relied on kernel.org kernels, and wanted >> bugfixes and security updates. It was not for new features or new >> hardware support. >> >> If people feel we should revisit this goal, then that's fine, and I have >> no objection to that. But until then, I think the rules that we have >> had in place for over the past 2 years should still remain in affect. > > I have to agree. I went back through my mbox and found vanishingly few > pci_id update patches. So it's not clear there's even a big issue. > Of course you didn't find many -- most people know that's not part of the -stable charter. If you asked for them you'd get them... - 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