From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 1/4] python: update requirements for Sphinx
Date: Sun, 8 Jun 2025 14:26:02 +0900 [thread overview]
Message-ID: <d1a5fe06-599d-4a04-a550-1c9927495516@daynix.com> (raw)
In-Reply-To: <20250606205009.584615-2-jsnow@redhat.com>
On 2025/06/07 5:50, John Snow wrote:
> In advance of actually bumping the build system requirements for Sphinx,
> bump the version used for the static analysis tests. Update the minimum
> requirements accordingly.
>
> This changes the test environment without actually changing the build
> requirements, and no extra changes are needed for the tests to continue
> passing.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
I didn't notice these files. Perhaps they are better to be documented
with pythondeps.toml.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2025-06-08 5:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 20:50 [PATCH 0/4] Docs: bump sphinx version to 6.2.1 John Snow
2025-06-06 20:50 ` [PATCH 1/4] python: update requirements for Sphinx John Snow
2025-06-08 5:26 ` Akihiko Odaki [this message]
2025-06-09 19:07 ` John Snow
2025-06-06 20:50 ` [PATCH 2/4] docs: Bump sphinx to 6.2.1 John Snow
2025-06-06 20:50 ` [PATCH 3/4] docs: Require sphinx>=6.2 John Snow
2025-06-06 20:50 ` [PATCH 4/4] MAINTAINERS: Add docs/requirements.txt John Snow
2025-06-11 17:01 ` [PATCH 0/4] Docs: bump sphinx version to 6.2.1 John Snow
2025-06-24 6:26 ` Markus Armbruster
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=d1a5fe06-599d-4a04-a550-1c9927495516@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).