From: "Darrick J. Wong" <djwong@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Subject: Re: [PATCH] Documentation: ext4: atomic_writes: Remove cross-reference labels
Date: Wed, 11 Jun 2025 18:09:42 -0700 [thread overview]
Message-ID: <20250612010942.GJ6179@frogsfrogsfrogs> (raw)
In-Reply-To: <aEoaJEhw5qHkd2_w@archie.me>
On Thu, Jun 12, 2025 at 07:07:00AM +0700, Bagas Sanjaya wrote:
> On Wed, Jun 11, 2025 at 11:05:17AM -0600, Jonathan Corbet wrote:
> > "Darrick J. Wong" <djwong@kernel.org> writes:
> >
> > > On Tue, Jun 10, 2025 at 04:11:59PM +0700, Bagas Sanjaya wrote:
> > >> Sphinx reports htmldocs warnings on ext4 atomic block writes docs:
> > >>
> > >> Documentation/filesystems/ext4/atomic_writes.rst:5: WARNING: duplicate label atomic_writes, other instance in Documentation/filesystems/ext4/atomic_writes.rst
> > >> Documentation/filesystems/ext4/atomic_writes.rst:207: WARNING: duplicate label atomic_write_bdev_support, other instance in Documentation/filesystems/ext4/atomic_writes.rst
> > >>
> > >> These warnings reference duplicated cross-reference labels to themselves in
> > >> the same doc, which are because atomic_writes.rst is transcluded in
> > >> overview.rst via include:: directive, thus the culprit docs get processed
> > >> twice.
> > >
> > > <confused> How is that possible? atomic_writes.rst is only "include::"d
> > > once in overview.rst. Is the file implicitly included through some
> > > other means?
> >
> > Sphinx wants to snarf up every .rst file it sees, regardless of whether
> > it is explicitly made part of the document tree. So it will pick up
> > atomic_writes.rst separately from the include.
Does that mean that overview.rst doesn't need to include the other files
at all?
> > This could be "fixed" by removing the .rst extension from the included
> > file. But, since there is no use of the atomic_writes label to begin
> > with, it's better to just take it out. The other fix, removing a cross
> > reference, is not entirely ideal, but there is little text between the
> > label and the reference.
>
> So removing the labels looks good to you, right?
I don't care that much either way, but if sphinx is going to include
every rst file implicitly then maybe we just get rid of the explicit
includes?
> Confused...
Me too.
--D
>
> --
> An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-06-12 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:11 [PATCH] Documentation: ext4: atomic_writes: Remove cross-reference labels Bagas Sanjaya
2025-06-11 16:48 ` Darrick J. Wong
2025-06-11 17:05 ` Jonathan Corbet
2025-06-12 0:07 ` Bagas Sanjaya
2025-06-12 1:09 ` Darrick J. Wong [this message]
2025-06-12 2:48 ` Bagas Sanjaya
2025-06-12 3:14 ` Bagas Sanjaya
2025-06-12 12:22 ` Jonathan Corbet
2025-06-12 12:20 ` Jonathan Corbet
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=20250612010942.GJ6179@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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).