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: Tue, 6 May 2008 03:54:45 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: Daniel Walker <dwalker@...sta.com> cc: Steven Rostedt <rostedt@...dmis.org>, Sven-Thorsten Dietrich <sven@...bigcorporation.com>, Remy Bohmer <linux@...mer.net>, LKML <linux-kernel@...r.kernel.org>, RT <linux-rt-users@...r.kernel.org>, Jon Masters <jonathan@...masters.org>, Ingo Molnar <mingo@...e.hu> Subject: Re: Preempt-RT patch for 2.6.25 On Mon, 5 May 2008, Daniel Walker wrote: > On Mon, 2008-05-05 at 23:01 +0200, Thomas Gleixner wrote: > > We have been there before. kernel development does not follow the "we > > want _now_" principle at all. Have you ever tried to yell at Linus "we > > want XYZ _now_" ? If you decide to try it, please keep me on CC - I > > want to enjoy the show. > > Kernel development is "What is available now?" not what is avaiable in > the future. > > If you want to reject code you better have a reason other than "We're > going to make some new code for that (some time in the future) sorry." You miss the point. We reject code which breaks existing functionality. > I'd like to hear Linus come out and say, "Sorry Thomas we can't include > your HRT cause we're getting a newer HRT in three years, so sorry about > that." Good point. HRT is mainline and it went through 300+ patch queues release cycles until the last bits got finaly merged. I appreciate your competent input how to do mainline development on large scale projects. In hindsight I regret that I did not hire you as my personal "get HRT merged" assistant. That would have saved me a lot of trouble and time. Thanks, tglx -- 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