From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"Wangnan (F)" <wangnan0@huawei.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Stephane Eranian <eranian@google.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Subject: Re: [RFC/PATCH] perf report: Show random usage tip on the help line
Date: Tue, 5 Jan 2016 22:49:04 -0300 [thread overview]
Message-ID: <20160106014904.GB6620@kernel.org> (raw)
In-Reply-To: <20160105232937.GA18895@sejong>
Em Wed, Jan 06, 2016 at 08:29:37AM +0900, Namhyung Kim escreveu:
> On Tue, Jan 05, 2016 at 09:59:11PM +0100, Andi Kleen wrote:
> > > > Thanks for the info. It's really easy doing that, nice..
> > > > I understand what he suggesting, but not why. :)
> > > Because then adding new tips will not require rebuilding the tool?
> > It would still need rebuilding if it was compiled in at build time.
> Right. Even if we allow to rebuild the tips at runtime, I doubt users
> want to update their documents..
Users don't have to update their documents if they don't, but having the
tips in a separate files allows them to do that if they want, or any
other method to update that tips file.
> > The main advantage of having the source in in Documentation is that it's easy
> > for users to read them all together (which may be useful)
> Agreed.
I agree that having the tips in a separate file, in the Documentation
directory is easy for users to read them all together, that is another
advantage, yes.
- Arnaldo
next prev parent reply other threads:[~2016-01-06 1:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 5:36 Namhyung Kim
2016-01-05 6:32 ` Wangnan (F)
2016-01-05 10:43 ` Namhyung Kim
2016-01-05 16:40 ` Arnaldo Carvalho de Melo
2016-01-05 19:19 ` Namhyung Kim
2016-01-05 20:55 ` Arnaldo Carvalho de Melo
2016-01-05 20:59 ` Andi Kleen
2016-01-05 23:29 ` Namhyung Kim
2016-01-06 1:49 ` Arnaldo Carvalho de Melo [this message]
2016-01-05 20:52 ` Andi Kleen
2016-01-05 23:37 ` Namhyung Kim
2016-01-06 1:51 ` Arnaldo Carvalho de Melo
2016-01-08 15:41 ` Arnaldo Carvalho de Melo
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=20160106014904.GB6620@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome