From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"mingo@elte.hu" <mingo@elte.hu>, David Ahern <dsahern@gmail.com>
Subject: Re: [BUG] perf list: --help option not implemented
Date: Mon, 22 Oct 2012 10:32:16 +0200 [thread overview]
Message-ID: <20121022083216.GA1758@krava.brq.redhat.com> (raw)
In-Reply-To: <87r4orj7zc.fsf@sejong.aot.lge.com>
On Mon, Oct 22, 2012 at 04:12:23PM +0900, Namhyung Kim wrote:
> Hi,
>
> On Fri, 19 Oct 2012 10:46:36 +0200, Jiri Olsa wrote:
> > On Fri, Oct 19, 2012 at 10:27:35AM +0200, Stephane Eranian wrote:
> >> Jiri,
> >>
> >> When I run perf list, I see:
> >>
> >> $ perf list
> >> ..
> >> rNNN [Raw hardware
> >> event descriptor]
> >> cpu/t1=v1[,t2=v2,t3 ...]/modifier [Raw hardware
> >> event descriptor]
> >> (see 'perf list --help' on how to encode it)
> >>
> >> But:
> >> $ perf list --help
> >> $
> >>
> >> Shows nothing. Looked at the code and I don't see where you handle the --help
> >> option. You need some help to figure out what the modifiers are.
> >>
> >> Am I missing something here?
> >
> > nope, it's not working.. added on my todo list ;-)
>
> I think it worked.
removed from my todo list ;)
seems like your patch adds man page as default for 'perf <command> --help'
sooo git-like ;) I dont mind..
jirka
next prev parent reply other threads:[~2012-10-22 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 8:27 Stephane Eranian
2012-10-19 8:46 ` Jiri Olsa
2012-10-22 7:12 ` Namhyung Kim
2012-10-22 8:32 ` Jiri Olsa [this message]
2012-10-22 13:26 ` David Ahern
2012-10-24 6:03 ` [tip:perf/urgent] perf help: Fix --help for builtins tip-bot for Namhyung Kim
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=20121022083216.GA1758@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--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
Powered by JetHome