From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>,
Markus Heiser <markus.heiser@darmarit.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH] doc-rst:sphinx-extensions: add metadata parallel-safe
Date: Thu, 01 Sep 2016 17:29:38 +0300 [thread overview]
Message-ID: <87inufzoa5.fsf@intel.com> (raw)
In-Reply-To: <20160901082136.597c37bf@lwn.net>
On Thu, 01 Sep 2016, Jonathan Corbet <corbet@lwn.net> wrote:
> On Wed, 24 Aug 2016 15:35:24 +0200
> Markus Heiser <markus.heiser@darmarit.de> wrote:
>
>> With metadata "parallel_read_safe = True" a extension is marked as
>> save for "parallel reading of source". This is needed if you want
>> build in parallel with N processes. E.g.:
>>
>> make SPHINXOPTS=-j4 htmldocs
>
> A definite improvement; applied to the docs tree, thanks.
The Sphinx docs say -jN "should be considered experimental" [1]. Any
idea *how* experimental that is, really? Could we add some -j by
default?
BR,
Jani.
[1] http://www.sphinx-doc.org/en/stable/invocation.html#invocation-of-sphinx-build
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-09-01 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 13:35 [PATCH] doc-rst:sphinx-extensions: add metadata parallel-safe Markus Heiser
2016-08-24 14:10 ` Mauro Carvalho Chehab
2016-09-01 14:21 ` Jonathan Corbet
2016-09-01 14:29 ` Jani Nikula [this message]
2016-09-01 16:22 ` Markus Heiser
2016-09-01 16:38 ` Markus Heiser
2016-09-02 14:54 ` 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=87inufzoa5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.