| 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: <481B0646.7090107@s5r6.in-berlin.de> Date: Fri, 02 May 2008 14:17:10 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: "Rafael J. Wysocki" <rjw@...k.pl> CC: Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org>, Willy Tarreau <w@....eu>, David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org, Jiri Slaby <jirislaby@...il.com> Subject: Re: Slow DOWN, please!!! Rafael J. Wysocki wrote: > A general rule that the trees people want you to pull during a merge window > should be tested in linux-next before, with no additional last minute changes, > may help. > > For this to work, though, the people will have to know in advance when the > merge window will start. Which may be helpful anyway. If I only release into my tree's for-next branch what I would release into my tree's for-linus if I was to send a merge request to Linus right in this moment, then I won't need advance notice of a merge window. IOW, treat -next everyday as if the merge window was open right now. I'm sure it is not that easy for the larger subsystems or the infrastructure trees. However, Linus' late -rc announcements are plenty of advance notice, at least for a merge period as long as two weeks. -- Stefan Richter -=====-==--- -=-= ---=- http://arcgraph.de/sr/ -- 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