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>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-doc@vger.kernel.org, Jani Nikula <jani.nikula@intel.com>
Subject: Re: Troubles with kernel-doc and RST files
Date: Tue, 19 Jul 2016 16:58:06 -0600 [thread overview]
Message-ID: <20160719165806.2ef581dc@lwn.net> (raw)
In-Reply-To: <F6675307-05E6-4101-92E9-69BC0232A939@darmarit.de>
On Tue, 19 Jul 2016 12:00:24 +0200
Markus Heiser <markus.heiser@darmarit.de> wrote:
> I recommend to consider to switch to the python version of the parser.
> I know, that there is a natural shyness about a reimplementation in python
> and thats why I offer to support it for a long time period .. it would
> be a joy for me ;-)
>
> If you interested in, I could send a RFC patch for this, if not please
> give the reasons why not.
We've had this discussion already... The problem is not with "python",
it's with "reimplementation". We have enough moving parts in this
transition already; tossing in a wholesale replacement of a tool that,
for all of its many faults, embodies a couple decades worth of experience
just doesn't seem like the right thing to do at this time.
I will be happy to entertain the idea of a new kernel-doc in the future;
trust me, I have no emotional attachment to the current one. But please
let's solidify what we have now first. There's enough stuff to deal with
as it is.
Thanks,
jon
next prev parent reply other threads:[~2016-07-19 22:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 13:01 Troubles with kernel-doc and RST files Mauro Carvalho Chehab
2016-07-18 2:37 ` Jonathan Corbet
2016-07-18 11:54 ` Mauro Carvalho Chehab
2016-07-19 10:00 ` Markus Heiser
2016-07-19 22:58 ` Jonathan Corbet [this message]
2016-07-20 5:32 ` Markus Heiser
2016-07-19 23:01 ` Jonathan Corbet
2016-07-20 0:08 ` Mauro Carvalho Chehab
2016-07-19 23:16 ` Jonathan Corbet
2016-07-20 0:09 ` Mauro Carvalho Chehab
2016-07-20 5:35 ` Markus Heiser
2016-07-19 23:30 ` Jonathan Corbet
2016-07-20 0:19 ` 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=20160719165806.2ef581dc@lwn.net \
--to=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--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 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.