From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>, linux-doc@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: Instruct LaTeX to cope with deeper nesting
Date: Tue, 20 Feb 2024 14:55:03 -0700 [thread overview]
Message-ID: <87msrug5s8.fsf@meer.lwn.net> (raw)
In-Reply-To: <685ad03e-b61c-4c1f-9080-c7298a7625dc@gmail.com>
Akira Yokosawa <akiyks@gmail.com> writes:
> On Mon, 19 Feb 2024 09:05:38 -0700, Jonathan Corbet wrote:
>> The addition of the XFS online fsck documentation starting with
>> commit a8f6c2e54ddc ("xfs: document the motivation for online fsck design")
>> added a deeper level of nesting than LaTeX is prepared to deal with. That
>> caused a pdfdocs build failure with the helpful "Too deeply nested" error
>> message buried deeply in Documentation/output/filesystems.log.
>>
>> Increase the "maxlistdepth" parameter to instruct LaTeX that it needs to
>> deal with the deeper nesting whether it wants to or not.
>>
>> Suggested-by: Akira Yokosawa <akiyks@gmail.com>
>> Link: https://lore.kernel.org/linux-doc/67f6ac60-7957-4b92-9d72-a08fbad0e028@gmail.com/
>> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
>
> Tested-by: Akira Yokosawa <akiyks@gmail.com>
Thanks
> And it seems this one might deserve
>
> Cc: stable@vger.kernel.org # v6.4
>
> too, in case someone tries "make pdfdocs" against 6.6.x LTS
> and 6.7.x stable branches.
Agreed, that was in my plans.
> Commit a8f6c2e54ddc did nothing wrong on its own, so a Fixes: tag
> is inappropriate here.
And a Fixes tag was definitely *not* in the plan.
Thanks,
jon
next prev parent reply other threads:[~2024-02-20 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:05 [PATCH] docs: Instruct LaTeX to cope with deeper nesting Jonathan Corbet
2024-02-20 15:28 ` Akira Yokosawa
2024-02-20 21:55 ` Jonathan Corbet [this message]
2024-02-21 1:44 ` Akira Yokosawa
2024-02-21 20:31 ` 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=87msrug5s8.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=vegard.nossum@oracle.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).