public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	Andi Kleen <andi@firstfloor.org>,
	Pekka Enberg <penberg@kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 3/3] perf report: Add --show-time-info option
Date: Mon, 2 Dec 2013 16:38:50 -0300	[thread overview]
Message-ID: <20131202193850.GC17149@ghostprotocols.net> (raw)
In-Reply-To: <529CDEA6.8000807@gmail.com>

Em Mon, Dec 02, 2013 at 12:25:26PM -0700, David Ahern escreveu:
> On 12/2/13, 12:23 PM, Arnaldo Carvalho de Melo wrote:
> >Em Mon, Dec 02, 2013 at 11:38:20PM +0900, Namhyung Kim escreveu:
> >>2013-12-02 (월), 09:33 -0300, Arnaldo Carvalho de Melo:
> >>>Em Mon, Dec 02, 2013 at 03:53:19PM +0900, Namhyung Kim escreveu:
> >>>>From: Namhyung Kim <namhyung.kim@lge.com>

> >>>>The --show-time-info option is for displaying elapsed sampling time

> >>>Isn't that too long? Can't we use just --time/-t?

> >>Hmm.. interesting.  Your previous feedback was to use longer and clearer
> >>option name. :)

> >>https://lkml.org/lkml/2013/11/18/198

> >Hey, longer and more descriptive names _when required_, in that case I
> >thought that even being longer --show-task-events would be better, but
> >here using --show-time-info the 'info' part looks superfluous, at least
> >to me, hence my suggestion/question :-)

> I thought -t/--time is going to be used to specify a time interval?
> Collect data for N-seconds, analyze some middle M-seconds.

Can you suggest a better name for the option being discussed?

Perhaps one of:

--show-event-time
--event-time

?

As a policy I think we should go on adding just long options and only
after there is a really strong case we should use a short option for
really, really popular options.

- Arnaldo

  reply	other threads:[~2013-12-02 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-02 19:23 [PATCH 3/3] perf report: Add --show-time-info option Arnaldo Carvalho de Melo
2013-12-02 19:25 ` David Ahern
2013-12-02 19:38   ` Arnaldo Carvalho de Melo [this message]
2013-12-02 19:58     ` David Ahern
2013-12-02 20:17       ` Arnaldo Carvalho de Melo
2013-12-02 20:22         ` David Ahern
2013-12-04 10:11         ` Ingo Molnar
2013-12-04 12:57           ` Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2013-12-02  6:53 [RFC 0/3] perf tools: Show time info (v1) Namhyung Kim
2013-12-02  6:53 ` [PATCH 3/3] perf report: Add --show-time-info option Namhyung Kim
2013-12-02 12:33   ` Arnaldo Carvalho de Melo
2013-12-02 14:38     ` 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=20131202193850.GC17149@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=penberg@kernel.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