From: Christoph Hellwig <hch@infradead.org>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Sphinx version dependencies?
Date: Fri, 20 Jul 2018 08:04:02 -0700 [thread overview]
Message-ID: <20180720150402.GA32320@infradead.org> (raw)
In-Reply-To: <44d73cd9926f58976a1269ff3cd3afb845ec84fa.camel@darmarit.de>
On Fri, Jul 20, 2018 at 09:30:33AM +0200, Markus Heiser wrote:
> We have this discussion over and over again an I believe we will have it again
> and again, as long as we do not change our POV .. building viewing formats is
> an application not a part of the Kernel.
Sorry, but this is complete and utter bullshit.
If that was the case we could skip all that RST stuff and just stick
to text files. If we want fancy docs it better behave like the rest
of the kernel and just works. python virtual environments are just
not going to cut it as they lead to a long-term maintainance nightmare.
next prev parent reply other threads:[~2018-07-20 15:04 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
2018-07-20 15:04 ` Christoph Hellwig [this message]
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=20180720150402.GA32320@infradead.org \
--to=hch@infradead.org \
--cc=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).