From: Donald Hunter <donald.hunter@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
linux-kernel@vger.kernel.org, Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
bpf@vger.kernel.org, llvm@lists.linux.dev,
workflows@vger.kernel.org
Subject: Re: [RFC 0/6] Raise the bar with regards to Python and Sphinx requirements
Date: Thu, 30 Jan 2025 09:33:30 +0000 [thread overview]
Message-ID: <m2zfj87ij9.fsf@gmail.com> (raw)
In-Reply-To: <cover.1738166451.git.mchehab+huawei@kernel.org> (Mauro Carvalho Chehab's message of "Wed, 29 Jan 2025 17:09:31 +0100")
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
> This series comes after https://lore.kernel.org/linux-doc/87a5b96296.fsf@trenco.lwn.net/T/#t
> It increases the minimal requirements for Sphinx and Python.
>
> Sphinx release dates:
>
> Release 2.4.0 (released Feb 09, 2020)
> Release 2.4.4 (released Mar 05, 2020) (current minimal requirement)
> Release 3.4.0 (released Dec 20, 2020)
> Release 3.4.3 (released Jan 08, 2021)
>
> (https://www.sphinx-doc.org/en/master/changes/index.html)
It's worth mentioning here that my fix for the C performance regression
landed in Sphinx 7.4.0. All versions from 3.0.0 to 7.3.x are much slower
for building the kernel docs. See #12162 here:
https://www.sphinx-doc.org/en/master/changes/7.4.html#id7
next prev parent reply other threads:[~2025-01-30 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 16:09 Mauro Carvalho Chehab
2025-01-29 16:09 ` [RFC 5/6] docs: changes: update Sphinx minimal version to 3.4.3 Mauro Carvalho Chehab
2025-01-29 16:09 ` [RFC 6/6] doc: changes: update Python minimal version Mauro Carvalho Chehab
2025-01-30 9:33 ` Donald Hunter [this message]
2025-01-30 14:31 ` [RFC 0/6] Raise the bar with regards to Python and Sphinx requirements 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=m2zfj87ij9.fsf@gmail.com \
--to=donald.hunter@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=justinstitt@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mchehab+huawei@kernel.org \
--cc=morbo@google.com \
--cc=ndesaulniers@google.com \
--cc=workflows@vger.kernel.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