From: Jonathan Corbet <corbet@lwn.net>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Matthew Wilcox <willy@infradead.org>
Cc: Adam Turner <aaturnerpython@outlook.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: Sphinx pre v3 -- removing support
Date: Fri, 03 Jun 2022 10:00:42 -0600 [thread overview]
Message-ID: <87tu91vis5.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220603154229.sj5sfeaehbkfzgin@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
> In the setup, I have it being installed as Sphinx~=2.0 with a comment:
>
> # Don't use Sphinx-3.x until upstream is happy using it
>
> I'm happy to upgrade that to a newer version if that condition no longer
> applies.
Upstream is "happy" in that it renders the documentation just fine and
we've dealt with the incompatibilities for our modules. My only
complaint is the speed, but presumably your automated system has no
trouble being patient :)
jon
next prev parent reply other threads:[~2022-06-03 16:00 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 [this message]
2022-06-03 16:26 ` Konstantin Ryabitsev
2022-06-03 21:50 ` Jonathan Corbet
2022-06-13 15:40 ` Konstantin Ryabitsev
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=87tu91vis5.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=aaturnerpython@outlook.com \
--cc=konstantin@linuxfoundation.org \
--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).