[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a8ad39nr.fsf@intel.com>
Date: Thu, 26 Jan 2017 21:26:16 +0200
From: Jani Nikula <jani.nikula@...el.com>
To: Jonathan Corbet <corbet@....net>,
Markus Heiser <markus.heiser@...marit.de>
Cc: Mauro Carvalho Chehab <mchehab@...radead.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Matthew Wilcox <mawilcox@...rosoft.com>,
"linux-doc \@ vger . kernel . org List" <linux-doc@...r.kernel.org>,
"linux-kernel \@ vger . kernel . org List"
<linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v1 2/6] kernel-doc: replace kernel-doc perl parser with a pure python one (WIP)
On Thu, 26 Jan 2017, Jonathan Corbet <corbet@....net> wrote:
> Give me a new kerneldoc that passes those tests, and I'll happily
> merge it. (I have some sympathy with the idea that we should look
> into other parsers, but I would not hold up a new kerneldoc that
> passed those tests on this basis alone.)
I'll just note in passing that having another parser that actually works
for our needs might be a pink unicorn pony. It might exist, it might
not, and someone would have to put in the hours to try to find it, tame
it, and bring it to the kernel. But it would be awesome to
have. Switching to a homebrew Python parser first does not preclude a
unicorn hunt later.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
Powered by blists - more mailing lists