From: Kees Cook <keescook@chromium.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] docs: Programmatically render MAINTAINERS into ReST
Date: Tue, 24 Sep 2019 14:51:33 -0700 [thread overview]
Message-ID: <201909241450.8A6B7E6EBF@keescook> (raw)
In-Reply-To: <87mueutb99.fsf@intel.com>
On Tue, Sep 24, 2019 at 10:16:18AM +0300, Jani Nikula wrote:
> I'd suggest making convert-maintainers.py a Sphinx extension, and
> handling all of this in Sphinx.
That's an excellent idea. I've done this now -- it simplifies things
quite a bit (though I had to beat my head against some odd behavioral
issues I tripped over inside docutils). I'll see the next version
shortly...
--
Kees Cook
next prev parent reply other threads:[~2019-09-24 21:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 22:43 [RFC][PATCH] docs: Programmatically render MAINTAINERS into ReST Kees Cook
2019-09-24 7:16 ` Jani Nikula
2019-09-24 21:51 ` Kees Cook [this message]
2019-09-24 10:08 ` Mauro Carvalho Chehab
2019-09-24 21:50 ` Kees Cook
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=201909241450.8A6B7E6EBF@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.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