From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Matthew Wilcox <willy@infradead.org>,
Adam Turner <aaturnerpython@outlook.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Sphinx pre v3 -- removing support
Date: Mon, 13 Jun 2022 11:40:59 -0400 [thread overview]
Message-ID: <20220613154059.oeb2kfp3j2amqat5@meerkat.local> (raw)
In-Reply-To: <871qw5ju1m.fsf@meer.lwn.net>
On Fri, Jun 03, 2022 at 03:50:29PM -0600, Jonathan Corbet wrote:
> > Indeed. So, should I go to 3.x, 4.x, or go all new and shiny with 5.x?
>
> Unless there is some subtle problem in the rendered docs that I'm not
> seeing, I don't think that there is any reason to go with the older
> releases. 5.0.1 seems to build things just fine, so I'd say go with the
> shiniest you can get.
Okay, https://docs.kernel.org/ is now built with Sphinx-5.0.1. At least, the
timestamps on the files are telling me so, because I can't see any other
changes. :)
-K
next prev parent reply other threads:[~2022-06-13 18:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 14:13 Sphinx pre v3 -- removing support Adam Turner
2022-06-03 14:21 ` Jonathan Corbet
2022-06-03 14:30 ` Adam Turner
2022-06-03 21:34 ` Jonathan Corbet
2022-06-03 15:22 ` Matthew Wilcox
2022-06-03 15:30 ` Adam Turner
2022-06-03 15:38 ` Matthew Wilcox
2022-06-03 15:42 ` Konstantin Ryabitsev
2022-06-03 16:00 ` Jonathan Corbet
2022-06-03 16:26 ` Konstantin Ryabitsev
2022-06-03 21:50 ` Jonathan Corbet
2022-06-13 15:40 ` Konstantin Ryabitsev [this message]
2022-06-13 16:00 ` Matthew Wilcox
2022-06-13 16:16 ` Adam Turner
2022-06-13 16:19 ` Matthew Wilcox
2022-06-03 22:11 ` Jonathan Corbet
2022-06-03 15:05 ` Akira Yokosawa
2022-06-03 15:27 ` Adam Turner
2022-06-03 15:44 ` Jani Nikula
2022-06-03 15:54 ` Adam Turner
2022-06-03 16:36 ` Akira Yokosawa
2022-06-03 19:05 ` Jani Nikula
2022-06-04 8:13 ` Mauro Carvalho Chehab
2022-07-02 11:23 ` Mauro Carvalho Chehab
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=20220613154059.oeb2kfp3j2amqat5@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=aaturnerpython@outlook.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=willy@infradead.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).