From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Purva Yeshi <purvayeshi550@gmail.com>,
mhiramat@kernel.org, corbet@lwn.net, skhan@linuxfoundation.org,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2] docs: trace: Refactor index documentation
Date: Thu, 13 Feb 2025 10:31:30 +0700 [thread overview]
Message-ID: <Z61nkk7X3jQJyzYX@archie.me> (raw)
In-Reply-To: <20250212095111.7e07b92e@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 991 bytes --]
On Wed, Feb 12, 2025 at 09:51:11AM -0500, Steven Rostedt wrote:
> On Wed, 12 Feb 2025 18:10:44 +0700
> Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> > > > +Introduction to Tracing
> > > > +-----------------------
> > > > +
> > > > +This section provides an overview of Linux tracing mechanisms
> > > > +and debugging approaches.
> > > >
> > > > .. toctree::
> > > > - :maxdepth: 2
> > > > + :maxdepth: 1
> > >
> > > I don't really know what the maxdepth gives here, but there was no mention
> > > in the change log why it had to be converted from 2 to 1.
> >
> > :maxdepth: specifies heading levels depth of the toctree. In this case,
> > the author wants only doc titles (hence 1), whereas 2 also includes
> > second-level (section) headings.
>
> As I'm the original author, I would like to know why there was a change.
>
Oops, I mean I'm referring to the patch author (Purva Yeshi).
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-02-13 3:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 14:14 [PATCH v2] docs: trace: Refactor index documentation Purva Yeshi
2025-02-10 22:45 ` Steven Rostedt
2025-02-12 11:10 ` Bagas Sanjaya
2025-02-12 14:51 ` Steven Rostedt
2025-02-13 3:31 ` Bagas Sanjaya [this message]
2025-02-13 11:56 ` Purva Yeshi
2025-02-13 16:47 ` Steven Rostedt
2025-02-13 19:12 ` 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=Z61nkk7X3jQJyzYX@archie.me \
--to=bagasdotme@gmail.com \
--cc=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