From: Jonathan Corbet <corbet@lwn.net>
To: Purva Yeshi <purvayeshi550@gmail.com>,
rostedt@goodmis.org, mhiramat@kernel.org
Cc: skhan@linuxfoundation.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, Purva Yeshi <purvayeshi550@gmail.com>
Subject: Re: [PATCH] docs: Move "debugging" section to the top in index.rst
Date: Tue, 04 Feb 2025 09:39:45 -0700 [thread overview]
Message-ID: <87bjvhhdf2.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250204133616.27694-1-purvayeshi550@gmail.com>
Purva Yeshi <purvayeshi550@gmail.com> writes:
> Move the "debugging" entry to the top in Documentation/trace/index.rst.
> Turn index.rst into a good starting point for people wanting to learn
> about tracing. Make it the first document users see, as it serves as a
> tracing tutorial
>
> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
> ---
> Documentation/trace/index.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
> index 2c991dc96ace..f3d235c8438b 100644
> --- a/Documentation/trace/index.rst
> +++ b/Documentation/trace/index.rst
> @@ -5,6 +5,7 @@ Linux Tracing Technologies
> .. toctree::
> :maxdepth: 2
>
> + debugging
> ftrace-design
> tracepoint-analysis
> ftrace
> @@ -24,7 +25,6 @@ Linux Tracing Technologies
> histogram
> histogram-design
> boottime-trace
> - debugging
> hwlat_detector
> osnoise-tracer
So I totally approve of improving our index.rst files. Without some
occasional maintenance, they become unorganized dumping grounds, and
Documentation/trace appears to be no exception.
This small change does not really help, though. Could I please
encourage you to consider bringing some real order to this page? As an
example, you could look at commit 270beb5b2aae from 6.13.
Thanks,
jon
next prev parent reply other threads:[~2025-02-04 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 13:36 [PATCH] docs: Move "debugging" section to the top in index.rst Purva Yeshi
2025-02-04 16:39 ` Jonathan Corbet [this message]
2025-02-05 13:31 ` Purva Yeshi
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=87bjvhhdf2.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=purvayeshi550@gmail.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
/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).