| 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
| ||
|
Date: Sat, 17 Nov 2007 02:15:11 +0300 From: Michael Tokarev <mjt@....msk.ru> To: Greg Kroah-Hartman <gregkh@...e.de> CC: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, torvalds@...ux-foundation.org, stable@...nel.org Subject: Re: Linux 2.6.23.3 Greg Kroah-Hartman wrote: > We (the -stable team) are announcing the release of the 2.6.23.3 kernel. > It contains a number of bugfixes for a number of architecture specific > issues. [.4, .5, .6 and .7 follows after .2 and .3] I've seen the bunch of patches posted for review - split to several series. But - out of curiocity - what's the reason to roll each series into each own stable release? Can't all .2...7 be combined into a single release (not counting .8 wich contains urgent security fixes)? (I mean, not with already rolled out stuff, but the original reasoning for split-releasing them (as opposed to split-reviewing)) Thanks. /mjt - 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