From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] kernel-shark: Separate trace-cmd and kernelshark documentations.
Date: Thu, 1 Aug 2019 09:25:54 -0400 [thread overview]
Message-ID: <20190801092554.3b32dc91@gandalf.local.home> (raw)
In-Reply-To: <20190801121955.20393-1-tz.stoyanov@gmail.com>
On Thu, 1 Aug 2019 15:19:55 +0300
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> KernelShark is going to be a stand alone package, separate from trace-cmd.
> The code is already in its own directory, but HTML and man page documents
> are still not separated.
> All KernelShark related documentation (HTML and the man page) is moved
> from Documentation/ to kernel-shark/doc/ directory.
> New targets are added to trace-cmd Makefile:
> doc_gui - build KernelShrak documentation
> doc_gui_clean - clean KernelShrak documentation
> install_doc_gui - install KernelShrak documentation
> The existing Makefile targets:
> doc, doc_clean, install_doc
> are modified to work only with trace-cmd documentation.
> The new Makefile targets must be used to build and install KernelShark docs.
>
> This change was requested by Bas van Dijk <v.dijk.bas@gmail.com>, to
> simplify packaging trace-cmd and kernelshark for nixpkgs, as two
> different packages.
>
> Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
> ---
> rename {Documentation => kernel-shark/doc}/HTML/images/kernelshark-logo.svg (100%)
When I first saw this, I questioned moving this out of Documentation.
But thinking about it more, it does make sense.
But can I ask you to keep the "Documentation" name?
It just seems more professional, and also stays in line with the
trace-cmd and Linux kernel "Documentation" directory name.
Thanks!
-- Steve
next prev parent reply other threads:[~2019-08-01 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 12:19 [PATCH] kernel-shark: Separate trace-cmd and kernelshark documentations Tzvetomir Stoyanov (VMware)
2019-08-01 13:25 ` Steven Rostedt [this message]
2019-08-05 12:39 ` Yordan Karadzhov (VMware)
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=20190801092554.3b32dc91@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@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;
as well as URLs for NNTP newsgroup(s).