From: Ingo Molnar <mingo@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <andi@firstfloor.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [RFC/PATCH v3] perf report: Show random usage tip on the help line
Date: Mon, 11 Jan 2016 11:55:51 +0100 [thread overview]
Message-ID: <20160111105550.GA300@gmail.com> (raw)
In-Reply-To: <20160109095001.GB7818@danjae.kornet>
* Namhyung Kim <namhyung@kernel.org> wrote:
> > On top of this, what do you think about only doing a single tip per day, the 'tip
> > of the day'? That would have two effects:
> >
> > - people who know all this already see this less
> >
> > - people who don't know all this will perhaps be more attentive, because a tip
> > for every report is more likely to get ignored.
> >
> > This could be done via a flag in ~/.perf/ or so.
>
> Not sure. Some people wanted to see more tips more frequently.
Fair enough!
I now had some experience with the tips, and they are not intrusive.
> I think the 'tip of the day' might be good for regular users, but many people
> just use perf when they need it and forget about it soon. For those people it'd
> be better to suggest useful tips more often.
Ok.
Thanks,
Ingo
next prev parent reply other threads:[~2016-01-11 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 11:41 [RFC/PATCH v3] perf report: Show random usage tip on the help line Namhyung Kim
2016-01-08 7:57 ` Ingo Molnar
2016-01-08 8:06 ` Ingo Molnar
2016-01-09 9:56 ` Namhyung Kim
2016-01-08 12:54 ` Arnaldo Carvalho de Melo
2016-01-09 9:55 ` Namhyung Kim
2016-01-09 9:50 ` Namhyung Kim
2016-01-11 10:55 ` Ingo Molnar [this message]
2016-01-09 16:40 ` [tip:perf/core] " 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=20160111105550.GA300@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@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 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.