From: Petr Vorel <pvorel@suse.cz>
To: linuxtestproject.agent@gmail.com
Cc: ltp@lists.linux.it
Subject: Re: [LTP] readthedocs: Update to Ubuntu 26.04, Sphinx 8.2.3
Date: Wed, 5 Aug 2026 13:12:13 +0200 [thread overview]
Message-ID: <20260805111213.GA543284@pevik> (raw)
In-Reply-To: <20260805103933.16659-1-linuxtestproject.agent@gmail.com>
> Hi Petr,
> On Aug 5, 2026, Petr Vorel wrote:
> > [PATCH 1/4] readthedocs: Update to Ubuntu 26.04, Sphinx 8.2.3
> --- [PATCH 2/4] ---
> > +# linuxdoc 20260504 is too verbose by default
> Could this change be folded into patch 3? At this point the requirements
> still pin linuxdoc 20240924, so the comment names a version that is not
> present in this commit, and the commit message explicitly depends on the
> following patch.
I deliberately wanted to fix it before updating linuxdoc + document the reason
even in the source code. But, if preferred, I can swap 2rd and 3nd patch.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-08-05 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 9:49 [LTP] [PATCH 0/4] readthedocs: Update to Ubuntu 26.04, Sphinx 8.2.3 Petr Vorel
2026-08-05 9:49 ` [LTP] [PATCH 1/4] " Petr Vorel
2026-08-05 10:39 ` [LTP] " linuxtestproject.agent
2026-08-05 11:12 ` Petr Vorel [this message]
2026-08-05 14:08 ` Andrea Cervesato via ltp
2026-08-05 14:58 ` Petr Vorel
2026-08-05 14:07 ` [LTP] [PATCH 1/4] " Andrea Cervesato via ltp
2026-08-05 9:49 ` [LTP] [PATCH 2/4] doc: Reduce default sphinx verbosity with -q Petr Vorel
2026-08-05 14:07 ` Andrea Cervesato via ltp
2026-08-05 9:49 ` [LTP] [PATCH 3/4] doc: Update linuxdoc, sphinxcontrib-spelling Petr Vorel
2026-08-05 14:07 ` Andrea Cervesato via ltp
2026-08-05 9:49 ` [LTP] [PATCH 4/4] tst_kvercmp.h: Further links to manpage Petr Vorel
2026-08-05 14:07 ` Andrea Cervesato via ltp
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=20260805111213.GA543284@pevik \
--to=pvorel@suse.cz \
--cc=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
/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