From: Namhyung Kim <namhyung@kernel.org>
To: Yunlong Song <yunlong.song@huawei.com>
Cc: a.p.zijlstra@chello.nl, paulus@samba.org, mingo@redhat.com,
acme@kernel.org, linux-kernel@vger.kernel.org,
wangnan0@huawei.com, artagnon@gmail.com, sriram.r@nokia.com,
adrian.hunter@intel.com, jolsa@kernel.org, dsahern@gmail.com
Subject: Re: [PATCH v2 1/3] perf help: Add options description to 'perf -h'
Date: Wed, 21 Oct 2015 10:57:14 +0900 [thread overview]
Message-ID: <20151021015714.GC628@sejong> (raw)
In-Reply-To: <5625A33D.8070001@huawei.com>
On Tue, Oct 20, 2015 at 10:13:17AM +0800, Yunlong Song wrote:
> On 2015/10/19 23:29, Namhyung Kim wrote:
> > Hi,
> >
> > On Thu, Oct 15, 2015 at 03:39:50PM +0800, Yunlong Song wrote:
> >> Add options description to 'perf -h' to make it consistent with other builtins
> >> (e.g., 'perf stat -h').
> >>
> >> Example:
> >>
> >> Before this patch:
> >>
> >> # perf -h
> >>
> >> usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]
> >>
> >> The most commonly used perf commands are:
> >> annotate Read perf.data (created by perf record) and display annotated code
> >> archive Create archive with object files with build-ids found in perf.data file
> >> bench General framework for benchmark suites
> >> buildid-cache Manage build-id cache.
> >> buildid-list List the buildids in a perf.data file
> >> <SNIP>
> >> test Runs sanity tests.
> >> timechart Tool to visualize total system behavior during a workload
> >> top System profiling tool.
> >> trace strace inspired tool
> >> probe Define new dynamic tracepoints
> >>
> >> See 'perf help COMMAND' for more information on a specific command.
> >>
> >> After this patch:
> >>
> >> # perf -h
> >>
> >> usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]
> >>
> >> --help help
> >> --version version
> >> --exec-path exec-path
> >> --html-path html-path
> >> --paginate paginate
> >> --no-pager no-pager
> >> --perf-dir perf-dir
> >> --work-tree work-tree
> >> --debugfs-dir debugfs-dir
> >> --buildid-dir buildid-dir
> >> --list-cmds list-cmds
> >> --list-opts list-opts
> >> --debug debug
> >
> > IMHO this *help* message is not very useful in its current form. Also
> > please consider updating Documentation/perf.txt too.
> >
> > Thanks,
> > Namhyung
>
> OK, I will update the struct option of perf to a more interpretative style soon.
In addition, --help and --version options are duplicate. And I think
--perf-dir and --work-tree options are never used. Also I doubt
anyone uses html help page with --html-path. Finally I think it'd be
better to hide --list-cmds and --list-opts options as they're only
intended to be used by completion scripts.
Thanks,
Namhyung
next prev parent reply other threads:[~2015-10-21 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444282190-13605-1-git-send-email-sriram.r@nokia.com>
2015-10-13 14:57 ` [PATCH 1/1] perf:Adding --list-opts to usage string Arnaldo Carvalho de Melo
2015-10-13 15:24 ` Ramkumar Ramachandra
2015-10-14 2:29 ` Yunlong Song
2015-10-14 3:10 ` Arnaldo Carvalho de Melo
2015-10-14 3:42 ` Namhyung Kim
2015-10-14 13:31 ` Yunlong Song
[not found] ` <CA+JHD92p0QUJGrqKTMYD8FUKj5tS9MUV_njsvoFwaHhsQevn_Q@mail.gmail.com>
2015-10-14 17:10 ` [PATCH 1/1] perf :redirection of usage strings to stdout Sriram Raghunathan
2015-10-15 7:22 ` Sriram Raghunathan
2015-10-15 7:11 ` [PATCH 1/1] perf:Adding --list-opts to usage string Yunlong Song
2015-10-14 13:44 ` [PATCH] perf help: Add options description to 'perf -h' Yunlong Song
2015-10-15 7:39 ` [PATCH v2 0/3] perf help: Make perf's help consistent with other builtins Yunlong Song
2015-10-15 7:39 ` [PATCH v2 1/3] perf help: Add options description to 'perf -h' Yunlong Song
2015-10-19 15:29 ` Namhyung Kim
2015-10-20 2:13 ` Yunlong Song
2015-10-21 1:57 ` Namhyung Kim [this message]
2015-10-15 7:39 ` [PATCH v2 2/3] perf help: Change 'usage' to 'Usage' for consistency Yunlong Song
2015-10-20 7:48 ` [tip:perf/core] " tip-bot for Yunlong Song
2015-10-15 7:39 ` [PATCH v2 3/3] perf help: Change the usage's stdout to stderr " Yunlong Song
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=20151021015714.GC628@sejong \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=artagnon@gmail.com \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=sriram.r@nokia.com \
--cc=wangnan0@huawei.com \
--cc=yunlong.song@huawei.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