From: Markus Heiser <markus.heiser@darmarit.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PULL] Docs for 4.13
Date: Tue, 4 Jul 2017 09:56:06 +0200 [thread overview]
Message-ID: <DAFD3CCB-2BDF-4713-9D3F-28264401F811@darmarit.de> (raw)
In-Reply-To: <CA+55aFxUVMM7HzGccqWk4ByRQAvJ11BN4raL2KL4J7GSXVx-7Q@mail.gmail.com>
Hi Jon,
> Am 04.07.2017 um 06:32 schrieb Linus Torvalds <torvalds@linux-foundation.org>:
[...]
> At the same time, lots of people run a lot of builds, and while I'd
> love to see warnings about docs failures, I am *not* willing to slow
> down my usual build enormously. I run "male allmodconfig" builds
> between every single pull during the merge window, and while it's
> often parallel with me looking at the problems, I don't really want to
> slow the build down too much. And the doc building is still *slow*.
>
> Is there some fast "just basic sanity checks" that would be more reasonable?
>
> Because one thing that the switch to sphinx has done is that the doc
> build environment seems saner (tool-wise). So now that kind of thing
> would at least be _possible_ to do in ways I don't think was
> reasonable with docbook.
Sphinx has 'dummy' builder since v1.4. I send a patch with a lintdocs
target [1]. Having a lintdocs target under which we can optimizes
linting might be useful at all and the 'dummy' builder is IMO a
good starting point ..
> And now docbook is finally gone. But sphinx isn't exactly a speed demon either.
The time-saving of the 'dummy' builder against the 'html' builder is about 40%.
[1] https://www.mail-archive.com/linux-doc@vger.kernel.org/msg13248.html
-- Markus --
next prev parent reply other threads:[~2017-07-04 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 13:20 Jonathan Corbet
2017-07-04 4:32 ` Linus Torvalds
2017-07-04 7:56 ` Markus Heiser [this message]
2017-07-04 19:24 ` Jonathan Corbet
2017-07-15 9:04 ` Daniel Vetter
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=DAFD3CCB-2BDF-4713-9D3F-28264401F811@darmarit.de \
--to=markus.heiser@darmarit.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®