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]
Date:	Mon, 25 Jul 2011 10:55:13 +0200
From:	Alexander Graf <agraf@...e.de>
To:	Pekka Enberg <penberg@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Jan Kiszka <jan.kiszka@....de>,
	torvalds@...ux-foundation.org, avi@...hat.com,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org, gorcunov@...il.com, levinsasha928@...il.com,
	asias.hejun@...il.com, prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1


On 25.07.2011, at 10:51, Pekka Enberg wrote:

> On Mon, Jul 25, 2011 at 11:44 AM, Alexander Graf <agraf@...e.de> wrote:
>>> For the same reasons we want tools/perf to be there.
>> 
>> Yeah, I want a pony too.
> 
> I can contact the Linux Foundation to see if we can arrange that.
> 
> Seriously, though, I don't understand your point. What is it? Do you
> not agree that perf benefited from being part of the Linux kernel
> tree? Or do you think it does not apply here?

I disagree with the assumption that putting something into the kernel tree benefits the project (except for maybe bumping its visibility, so it potentially kills competition again). If however it's true, then we should analyze why exactly projects benefit from being in the kernel tree, so we can maybe find a good solution to achieve the same differently.

The approach "let's move everyting into tools/" simply doesn't scale.


Alex

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