From: Christoph Hellwig <hch@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, acme@infradead.org,
Andi Kleen <ak@linux.intel.com>,
Namhyung Kim <namhyung.kim@lge.com>,
peterz@infradead.org
Subject: Re: [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable
Date: Mon, 5 Aug 2013 01:34:34 -0700 [thread overview]
Message-ID: <20130805083434.GA20606@infradead.org> (raw)
In-Reply-To: <20130805083132.GE26746@gmail.com>
On Mon, Aug 05, 2013 at 10:31:32AM +0200, Ingo Molnar wrote:
> Nonsense, a distro, if it truly worried about this, could create two
> packages already, there's no need to expose configuration options in the
> binary name itself and burden users with the separation. I sometimes
> switch the UI frontend of perf depending on the workflow and the terminal,
> it would be highly annoying if the binary name was changed to expose
> configuration options.
Which means you'd have to use a different tool name or have incompatible
packages, both of which aren't desirable.
> The thing is, you strongly objected to perf itself when we offered it up
> for an upstream merge and I'm not surprised you still don't like it.
I strongly objected to adding it to the kernel tree, and I still stand
to that opinion because it makes using perf much more painful than it
needs to be. I never disliked perf itself and use it frequently now
that I can bypass some of the pains by just using an older distro
package.
But I'd much rather get this back to technical discussions than personal
attacks..
next prev parent reply other threads:[~2013-08-05 8:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 2:22 [PATCH] RFC: perf, tools: Move gtk browser into separate perfgtk executable Andi Kleen
2013-08-05 8:16 ` Ingo Molnar
2013-08-05 8:23 ` Christoph Hellwig
2013-08-05 8:31 ` Ingo Molnar
2013-08-05 8:34 ` Christoph Hellwig [this message]
2013-08-05 9:08 ` Ingo Molnar
2013-08-06 6:19 ` Christoph Hellwig
2013-08-12 18:19 ` Ingo Molnar
2013-08-12 19:25 ` Vince Weaver
2013-08-13 10:48 ` Ingo Molnar
2013-08-13 12:11 ` Arnaldo Carvalho de Melo
2013-08-13 16:00 ` Ingo Molnar
2013-08-13 21:57 ` Vince Weaver
2013-08-13 22:17 ` Andi Kleen
2013-08-14 14:13 ` Arnaldo Carvalho de Melo
2013-08-14 14:20 ` Ingo Molnar
2013-08-13 14:03 ` Vince Weaver
2013-08-13 16:04 ` Ingo Molnar
2013-08-05 9:08 ` Namhyung Kim
2013-08-05 9:12 ` Ingo Molnar
2013-08-05 9:18 ` Pekka Enberg
2013-08-05 19:10 ` Andi Kleen
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=20130805083434.GA20606@infradead.org \
--to=hch@infradead.org \
--cc=acme@infradead.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.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