From: John Kacur <jkacur@redhat.com>
To: Wenji Huang <wenji.huang@oracle.com>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com, mingo@elte.hu,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] perf: fix incorrect return value for else case
Date: Mon, 21 Dec 2009 16:23:17 +0100 [thread overview]
Message-ID: <520f0cf10912210723j1ac91183n3d7970b96b95ef23@mail.gmail.com> (raw)
In-Reply-To: <1261387359-1933-1-git-send-email-wenji.huang@oracle.com>
On Mon, Dec 21, 2009 at 10:22 AM, Wenji Huang <wenji.huang@oracle.com> wrote:
> Return original cmd instead of adding prefix.
>
> Signed-off-by: Wenji Huang <wenji.huang@oracle.com>
> ---
> tools/perf/builtin-help.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/tools/perf/builtin-help.c b/tools/perf/builtin-help.c
> index 9f810b1..ca77df5 100644
> --- a/tools/perf/builtin-help.c
> +++ b/tools/perf/builtin-help.c
> @@ -317,7 +317,7 @@ static const char *cmd_to_page(const char *perf_cmd)
> else if (is_perf_command(perf_cmd))
> return prepend("perf-", perf_cmd);
> else
> - return prepend("perf-", perf_cmd);
> + return perf_cmd;
> }
>
> static void setup_man_path(void)
> --
> 1.5.6
Sorry - I believe we should NAK this patch.
It would turn the following
./perf nonsuchcmd --help
No manual entry for perf-nonsuchcmd
into
./perf nonsuchcmd --help
No manual entry for nonsuchcmd
The former is correct, the name of the man page includes the prefix "perf-"
NAK
(cc-ing Frederic in case he sees it differently)
Thank You
John Kacur
next prev parent reply other threads:[~2009-12-21 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 9:22 Wenji Huang
2009-12-21 15:23 ` John Kacur [this message]
2009-12-22 1:27 ` Wenji Huang
2009-12-30 22:12 ` Frederic Weisbecker
2010-01-13 8:45 ` Ingo Molnar
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=520f0cf10912210723j1ac91183n3d7970b96b95ef23@mail.gmail.com \
--to=jkacur@redhat.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wenji.huang@oracle.com \
/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®