All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] perf, record: Ammend option summaries
Date: Thu, 11 Jun 2015 10:58:51 -0300	[thread overview]
Message-ID: <20150611135851.GA2696@kernel.org> (raw)
In-Reply-To: <20150611084619.GR19282@twins.programming.kicks-ass.net>

Em Thu, Jun 11, 2015 at 10:46:19AM +0200, Peter Zijlstra escreveu:
> On Wed, Jun 10, 2015 at 02:27:43PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Jun 10, 2015 at 04:48:50PM +0200, Peter Zijlstra escreveu:
> > > Because there's too many options and I cannot read, I frequently get
> > > confused between -c and -P, and try to do things like:

> > >   perf record -P 50000 -- foo

> > > Which does not work; try and make the option description slightly longer
> > > and hopefully less confusing.

> > Thanks, I'll check and update tools/perf/Documentation/perf-record.txt,
> > i.e. the man page.

> Thanks, I always forget that stuff even exists. I further get totally
> annoyed every time I do: perf record --help and it vomits on me.

> Could we please make -h and --help do the exact same thing?

Well, right now it tries to read the man-page, that if not installed,
will bail out straight away, I guess this is something we inherited from
the git code base, long ago.

Ok, I think I'll try to use both, i.e. make 'perf foo --help' fall back
to '-h' when the man page is not found, with an extra warning, at the
top, when doing that.

- Arnaldo

  reply	other threads:[~2015-06-11 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 14:48 [PATCH] perf, record: Ammend option summaries Peter Zijlstra
2015-06-10 17:27 ` Arnaldo Carvalho de Melo
2015-06-11  8:46   ` Peter Zijlstra
2015-06-11 13:58     ` Arnaldo Carvalho de Melo [this message]
2015-06-12  8:49 ` [tip:perf/core] perf record: Amend " tip-bot for Peter Zijlstra

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=20150611135851.GA2696@kernel.org \
    --to=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.