[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160106014904.GB6620@kernel.org>
Date: Tue, 5 Jan 2016 22:49:04 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Andi Kleen <andi@...stfloor.org>,
"Wangnan (F)" <wangnan0@...wei.com>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Jiri Olsa <jolsa@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Stephane Eranian <eranian@...gle.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Subject: Re: [RFC/PATCH] perf report: Show random usage tip on the help line
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists