From: David Ahern <dsahern@gmail.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@gmail.com>,
Stephane Eranian <eranian@google.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] perf tool: save cmdline from user in file header vs what is passed to record
Date: Fri, 06 Jul 2012 11:19:10 -0600 [thread overview]
Message-ID: <4FF71E0E.8010602@gmail.com> (raw)
In-Reply-To: <20120706171735.GH7533@infradead.org>
On 7/6/12 11:17 AM, Arnaldo Carvalho de Melo wrote:
> Can you please state for what branch, perf/urgent (i.e. current merge
> window) or perf/core (next), this is intended? I usually have been
> making the call, but having feedback from the submitter can help things
> and help meet expectations more frequently.
>
> I'd say this one should be for perf/core, as it is not so critical, what
> do you think?
right, need to add that tag. It's not a regression, just an oversight on
the original implementation. perf/core is the right branch.
David
next prev parent reply other threads:[~2012-07-06 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 4:09 [PATCH] perf tool: save cmdline from user in file header vs what is passed to record David Ahern
2012-07-06 17:17 ` Arnaldo Carvalho de Melo
2012-07-06 17:19 ` David Ahern [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 2:53 David Ahern
2012-07-03 4:08 David Ahern
2012-07-05 15:48 ` Stephane Eranian
2012-07-05 16:47 ` David Ahern
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=4FF71E0E.8010602@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.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