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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.0.999.0707310842520.4161@woody.linux-foundation.org>
Date:	Tue, 31 Jul 2007 08:44:48 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bill Huey <billh@...ppy.monkey.org>
cc:	George Sescher <gesacs@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Kasper Sandberg <lkml@...anurb.dk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	CK Mailinglist <ck@....kolivas.org>
Subject: Re: Linus 2.6.23-rc1



On Tue, 31 Jul 2007, Bill Huey wrote:
> 
> Here's the problem, *a lot* of folks can do scheduler development in and
> outside community, so what's with exclusive-only attitude towards the
> scheduler ?

There is no exclusive-only attitude towards the scheduler.

If you send me small and obvious improvements, they'll get applied to the 
scheduler, exactly the same way they get applied to anything else.

And if you try to rewrite everything, and do it on your own, and then 
don't even send me a patch, it also won't get applied. 

Surprise?

			Linus
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ