From: Namhyung Kim <namhyung@kernel.org>
To: Taewoong Song <treeze.taeung@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
jolsa@redhat.com
Subject: Re: [PATCH 1/2] perf tools: Add 'perf-config' command
Date: Sun, 19 Apr 2015 12:27:03 +0900 [thread overview]
Message-ID: <20150419032703.GA10169@danjae.kornet> (raw)
In-Reply-To: <5CB87CAF-B6EE-4AE0-BC3C-45CEF14C28EC@gmail.com>
Hi Taeung,
On Sat, Apr 18, 2015 at 02:02:08PM +0900, Taewoong Song wrote:
> Hi, Namhyung
>
> Thanks for your review and advices :)
> There is a question which may be weird, followed by
>
> > On Apr 13, 2015, at 3:16 PM, Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > Hi Taeung,
> >
> > On Sun, Apr 12, 2015 at 11:44:48PM +0900, Taeung Song wrote:
> >> The perf configuration file contains many variables which can make
> >> the perf command's action more effective and more skilful.
> >> But looking through state of configuration is difficult and
> >> there's no knowing what kind of other variables except variables in perfconfig.example exist.
> >> So This patch adds 'perf-config' command with '--all' option and a document for it.
> >>
> >> Signed-off-by: Taeung Song <treeze.taeung@gmail.com <mailto:treeze.taeung@gmail.com>>
> >> ---
> >
> > Thanks for your work!
> >
> > I think the documentation updates need to be shared with tools
> > manpages, or at least they can point to this document for details.
> > This can be further work though. ;-)
> >
>
> Sorry I don’t understand this share very well.
> How can I share the documentation with tools manpages ?
I mean you can add a description for some feature to link the config
document or vice versa. Many of those description can be added to the
tool manpage or cross-reference config option at least.
For example, I sent a patch for children overhead documentation so you
can just add 'see perf-report(1) for more details' into the
description of the config option instead of repeating the whole
contents. Or use asciidoc's 'include' macro to include the (part of)
doc directly if possible.
>
> And are there people who can help the document to be modified with more detail info ?
> Are they contributors for doc ?
Unfortunately, very few people donated their time to improve the
documentation until now.
Thanks,
Namhyung
next prev parent reply other threads:[~2015-04-19 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 14:44 Taeung Song
2015-04-12 14:44 ` [PATCH 2/2] perf tools: Add a option 'remove' to perf-config and features which get or set a config variable Taeung Song
2015-04-13 6:55 ` Namhyung Kim
[not found] ` <6F8981BC-A058-4D84-93FC-B7CB8ADDCC53@gmail.com>
2015-04-19 3:42 ` Namhyung Kim
2015-04-13 6:16 ` [PATCH 1/2] perf tools: Add 'perf-config' command Namhyung Kim
[not found] ` <5CB87CAF-B6EE-4AE0-BC3C-45CEF14C28EC@gmail.com>
2015-04-19 3:27 ` Namhyung Kim [this message]
[not found] ` <70EA4387-5059-4026-8819-039474865EEE@gmail.com>
2015-04-19 3:34 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2015-04-09 14:26 Taeung Song
2015-04-09 15:57 ` Arnaldo Carvalho de Melo
2015-04-10 8:53 ` Jiri Olsa
2015-04-04 17:41 Taeung Song
2015-04-07 17:57 ` Jiri Olsa
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=20150419032703.GA10169@danjae.kornet \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=treeze.taeung@gmail.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
all inboxes | Powered by JetHome®