From: Jonathan Corbet <corbet@lwn.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Markus Heiser <markus.heiser@darmarit.de>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Sphinx version dependencies?
Date: Sat, 21 Jul 2018 04:38:47 -0600 [thread overview]
Message-ID: <20180721043847.59a2cb0a@lwn.net> (raw)
In-Reply-To: <20180720131206.GM30706@thunk.org>
On Fri, 20 Jul 2018 09:12:06 -0400
"Theodore Y. Ts'o" <tytso@mit.edu> wrote:
> A forth solution is to force everyone to use something correleted to
> what the community distro's are packaging, but roughly every 12-18
> months, we leapfrog to a newer version of Sphinx. This decreases the
> continuous upgrade burden, but doesn't make it go away.
[I'm mostly AFK at the moment, so haven't been following this discussion
in anything approaching real time].
The above is roughly what I've been aiming for; I'd really like for
people to be able to just build the docs without having to go beyond
their distribution's repos. It gets challenging at times because Kids
These Days seem to have a different view on issues like long-term
compatibility. But we've mostly done it; it's pretty rare that we've had
docs build problems that have been tied to a specific version of Sphinx.
You all just got lucky :)
jon
next prev parent reply other threads:[~2018-07-21 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180719181556.GA21435@thunk.org>
[not found] ` <20180719190400.GB4800@magnolia>
2018-07-20 7:30 ` Sphinx version dependencies? Markus Heiser
2018-07-20 13:12 ` Theodore Y. Ts'o
2018-07-20 13:45 ` Markus Heiser
2018-07-20 14:52 ` Theodore Y. Ts'o
2018-07-20 16:00 ` Markus Heiser
2018-07-20 16:44 ` Darrick J. Wong
2018-07-20 16:58 ` Markus Heiser
2018-07-20 17:10 ` Darrick J. Wong
2018-07-20 20:43 ` Theodore Y. Ts'o
2018-07-20 21:28 ` Markus Heiser
2018-07-21 10:38 ` Jonathan Corbet [this message]
2018-07-20 15:04 ` Christoph Hellwig
2018-07-20 16:28 ` Markus Heiser
2018-07-20 17:08 ` Darrick J. Wong
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=20180721043847.59a2cb0a@lwn.net \
--to=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=tytso@mit.edu \
/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).