From: Jonathan Corbet <corbet@lwn.net>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 0/3] doc-rst: more generic way to build only sphinx sub-folders
Date: Tue, 9 Aug 2016 09:21:08 -0600 [thread overview]
Message-ID: <20160809092108.266f37c2@lwn.net> (raw)
In-Reply-To: <1470662100-6927-1-git-send-email-markus.heiser@darmarit.de>
On Mon, 8 Aug 2016 15:14:57 +0200
Markus Heiser <markus.heiser@darmarit.de> wrote:
> this is my approach for a more generic way to build only sphinx sub-folders, we
> discussed in [1]. The last patch adds a minimal conf.py to the gpu folder, if
> you don't want to patch the gpu folder drop it.
I haven't had a chance to really mess with this yet, but it seems like a
reasonable solution. Mauro, does it give you what you need?
Thanks,
jon
next prev parent reply other threads:[~2016-08-09 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 13:14 [PATCH 0/3] doc-rst: more generic way to build only sphinx sub-folders Markus Heiser
2016-08-08 13:14 ` [PATCH 1/3] doc-rst: " Markus Heiser
2016-08-12 21:20 ` Jonathan Corbet
2016-08-13 14:38 ` Markus Heiser
2016-08-08 13:14 ` [PATCH 2/3] doc-rst: add stand-alone conf.py to media folder Markus Heiser
2016-08-08 13:15 ` [PATCH 3/3] doc-rst: add stand-alone conf.py to gpu folder Markus Heiser
2016-08-09 15:21 ` Jonathan Corbet [this message]
2016-08-09 18:02 ` [PATCH 0/3] doc-rst: more generic way to build only sphinx sub-folders Mauro Carvalho Chehab
2016-08-09 18:37 ` Markus Heiser
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=20160809092108.266f37c2@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
/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