From: Akira Yokosawa <akiyks@gmail.com>
To: Vegard Nossum <vegard.nossum@oracle.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH] docs: drop the version constraints for sphinx and dependencies
Date: Fri, 1 Mar 2024 11:33:19 +0900 [thread overview]
Message-ID: <fc6563ac-e705-48ff-9581-ac4154a064ac@gmail.com> (raw)
In-Reply-To: <e6441dc1-6821-4514-b285-ebc24114aece@oracle.com>
On Thu, 29 Feb 2024 15:39:31 +0100, Vegard Nossum wrote:
> [...]
>
> $ scripts/sphinx-pre-install
> Detected OS: Ubuntu 22.04.3 LTS.
> Sphinx version: 4.3.2
>
>
> All optional dependencies are met.
> Needed package dependencies are met.
>
>
> One remark I have is that it didn't encourage me to upgrade to 7.2.6 in
> the last one (using the system Sphinx 4.3.2) although it did for the
> 2.4.4 virtualenv. Maybe that's expected. I didn't look into it. Anyway,
Yes, it's expected.
Sphinx 3.4.3 provided as distro packages of Debian 11 (bullseye),
RHEL 9, and so on is good enough for kernel documentation.
Suggesting upgrade to a latest release would be noisy.
The version is assigned to $rec_version in sphinx-pre-install.
As a fix to requirements.txt for v6.8, this looks to me like a nice
minimal change.
Lukas, many thanks for doing this.
Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
Thanks, Akira
next prev parent reply other threads:[~2024-03-01 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 13:14 [PATCH] docs: drop the version constraints for sphinx and dependencies Lukas Bulwahn
2024-02-27 13:25 ` Lukas Bulwahn
2024-02-28 22:16 ` Jonathan Corbet
2024-02-29 14:39 ` Vegard Nossum
2024-03-01 2:33 ` Akira Yokosawa [this message]
2024-03-01 14:19 ` Lukas Bulwahn
2024-03-01 14:22 ` Lukas Bulwahn
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=fc6563ac-e705-48ff-9581-ac4154a064ac@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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).