From: Alexander Graf <agraf@suse.de>
To: Pekka Enberg <penberg@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Jan Kiszka <jan.kiszka@web.de>,
torvalds@linux-foundation.org, avi@redhat.com,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, gorcunov@gmail.com, levinsasha928@gmail.com,
asias.hejun@gmail.com, prasadjoshi124@gmail.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1
Date: Mon, 25 Jul 2011 10:55:13 +0200 [thread overview]
Message-ID: <7A93237F-CC6D-4536-81CD-3580718D5C1D@suse.de> (raw)
In-Reply-To: <CAOJsxLEg16wEJ69x0HeCXhD-U26vD8t5Uqj2OJvaCM-xhrQBzQ@mail.gmail.com>
On 25.07.2011, at 10:51, Pekka Enberg wrote:
> On Mon, Jul 25, 2011 at 11:44 AM, Alexander Graf <agraf@suse.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
next prev parent reply other threads:[~2011-07-25 8:55 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 20:37 Pekka Enberg
2011-07-24 23:12 ` Jan Kiszka
2011-07-25 7:37 ` Pekka Enberg
2011-07-25 7:53 ` Ingo Molnar
2011-07-25 8:14 ` Alexander Graf
2011-07-25 8:23 ` Pekka Enberg
2011-07-25 8:31 ` Alexander Graf
2011-07-25 8:35 ` Avi Kivity
2011-07-25 13:10 ` Joerg Roedel
2011-07-25 15:05 ` Avi Kivity
2011-07-25 8:37 ` Pekka Enberg
2011-07-25 8:44 ` Alexander Graf
2011-07-25 8:51 ` Pekka Enberg
2011-07-25 8:55 ` Alexander Graf [this message]
2011-07-25 9:16 ` Ingo Molnar
2011-07-25 9:14 ` Ingo Molnar
2011-07-25 8:30 ` Pekka Enberg
2011-07-25 8:37 ` Alexander Graf
2011-07-25 8:47 ` Pekka Enberg
2011-07-25 9:06 ` Alexander Graf
2011-07-25 12:45 ` Pekka Enberg
2011-07-25 12:47 ` Avi Kivity
2011-07-25 12:51 ` Sasha Levin
2011-07-25 12:54 ` Alexander Graf
2011-07-25 13:14 ` Sasha Levin
2011-07-25 12:51 ` Alexander Graf
2011-07-25 13:09 ` Pekka Enberg
2011-07-25 13:29 ` Alexander Graf
2011-07-25 9:26 ` Ingo Molnar
2011-07-25 9:42 ` Alexander Graf
2011-07-25 10:16 ` Ingo Molnar
2011-07-25 10:21 ` Alexander Graf
2011-07-25 10:35 ` Ingo Molnar
2011-07-25 10:47 ` Ingo Molnar
2011-07-25 12:24 ` Kevin Wolf
2011-07-25 12:41 ` Pekka Enberg
2011-07-25 12:46 ` Avi Kivity
2011-07-25 8:54 ` Ingo Molnar
2011-07-25 8:59 ` Ingo Molnar
2011-07-25 9:03 ` Alexander Graf
2011-07-25 9:41 ` Ingo Molnar
2011-07-25 9:46 ` Alexander Graf
2011-07-25 10:28 ` Ingo Molnar
2011-07-25 9:48 ` Avi Kivity
2011-07-25 10:03 ` Ingo Molnar
2011-07-25 10:17 ` Avi Kivity
2011-07-25 10:29 ` Ingo Molnar
2011-07-25 11:26 ` Olivier Galibert
2011-07-25 10:38 ` Christoph Hellwig
2011-07-25 11:08 ` Ingo Molnar
2011-07-25 11:24 ` Christoph Hellwig
2011-07-25 11:32 ` Ingo Molnar
2011-07-25 11:34 ` Olivier Galibert
2011-07-25 11:41 ` Christoph Hellwig
2011-07-25 12:09 ` Ingo Molnar
2011-07-25 12:36 ` Pekka Enberg
2011-07-25 19:21 ` david
2011-07-25 18:24 ` Jan Kiszka
2011-07-25 19:43 ` Pekka Enberg
2011-07-25 7:50 ` Sasha Levin
2011-07-25 8:34 ` Alexander Graf
2011-07-25 12:59 ` Paolo Bonzini
2011-07-25 13:16 ` Anthony Liguori
2011-07-25 1:19 ` Anthony Liguori
2011-07-25 7:27 ` Pekka Enberg
2011-07-25 7:36 ` Avi Kivity
2011-07-25 7:39 ` Pekka Enberg
2011-07-25 7:55 ` Sasha Levin
[not found] ` <CAFO3S428qqUAu19QjPxDDAVv+eJSX0MEfYp5y03znNi6XbEtTg@mail.gmail.com>
2011-07-25 8:11 ` Ingo Molnar
2011-07-25 8:17 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7A93237F-CC6D-4536-81CD-3580718D5C1D@suse.de \
--to=agraf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®