| 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: <20070719100346.a9e8b12b.akpm@linux-foundation.org> Date: Thu, 19 Jul 2007 10:03:46 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: "Josh Boyer" <jwboyer@...il.com> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, LKML <linux-kernel@...r.kernel.org>, "Nigel Cunningham" <nigel@...el.suspend2.net>, "Oleg Nesterov" <oleg@...sign.ru>, "Pavel Machek" <pavel@....cz> Subject: Re: [PATCH -mm 0/5] Freezer update On Thu, 19 Jul 2007 11:30:54 -0500 "Josh Boyer" <jwboyer@...il.com> wrote: > On 7/18/07, Andrew Morton <akpm@...ux-foundation.org> wrote: > > > > so please consider them as 2.6.23 material. > > > > The door for new 2.6.23 material shut two weeks ago. Here, at least. > > So do you have a general guideline as to when you'd like patches sent > to you for the next merge window? The releases are fairly > predictable, so perhaps something like one of the later -rc candidates > for the upcoming release? > > E.g. patches for 2.6.24 should be to you by 2.6.23-rc<N>? That sounds about right. But nothing is cast in stone here: one needs to take into account the urgency/desirability of the change, the perceived benefit and risk, etc. I do prefer that material has been out in at least one -mm release before it goes mainline. - 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