From: Jonathan Corbet <corbet@lwn.net>
To: Vishal Singh <vishalrajput96156@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Vishal Singh <vishalrajput96156@gmail.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [PATCH] docs: conf.py: drop stale FIXME about pdf index size
Date: Tue, 06 Jan 2026 15:02:19 -0700 [thread overview]
Message-ID: <87eco2csd0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20251223121543.401133-1-vishalrajput96156@gmail.com>
Vishal Singh <vishalrajput96156@gmail.com> writes:
CC += Jani
> The comment describes intentional behavior and does not indicate
> unfinished work. Remove the FIXME marker and keep it as a normal
> explanatory comment.
>
> Signed-off-by: Vishal Singh <vishalrajput96156@gmail.com>
> ---
> Documentation/conf.py | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/conf.py b/Documentation/conf.py
> index 1ea2ae5c6276..7e0817469e86 100644
> --- a/Documentation/conf.py
> +++ b/Documentation/conf.py
> @@ -572,9 +572,8 @@ epub_exclude_files = ["search.html"]
> #
> # See the Sphinx chapter of https://ralsina.me/static/manual.pdf
> #
> -# FIXME: Do not add the index file here; the result will be too big. Adding
> -# multiple PDF files here actually tries to get the cross-referencing right
> -# *between* PDF files.
> +# Do not add the index file here; the result would be too big. Adding multiple
> +# PDF files here tries to keep cross-referencing correct *between* PDF files.
I think the comment doesn't have much to tell people either way, I
wonder if it can just go altogether. Jani, what problem is actually
being described here?
Thanks,
jon
next prev parent reply other threads:[~2026-01-06 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 12:15 [PATCH] docs: conf.py: drop stale FIXME about pdf index size Vishal Singh
2026-01-06 22:02 ` Jonathan Corbet [this message]
2026-01-07 9:09 ` Jani Nikula
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=87eco2csd0.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishalrajput96156@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