From: Randy Dunlap <rdunlap@infradead.org>
To: "Jonathan Corbet" <corbet@lwn.net>,
"Tomasz Warniełło" <tomasz.warniello@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts: kernel-doc: Major kernel-doc rework
Date: Thu, 17 Feb 2022 09:50:21 -0800 [thread overview]
Message-ID: <f30311b5-1b30-ed79-ca66-4359a8f9586b@infradead.org> (raw)
In-Reply-To: <87bkz51l2g.fsf@meer.lwn.net>
On 2/17/22 09:04, Jonathan Corbet wrote:
> Tomasz Warniełło <tomasz.warniello@gmail.com> writes:
>
>> I will prepare the POD part. As for the rest, you will need a porter if you
>> decide this is the way to go. I could help with explanations if something is
>> unclear and as long as the questions come soon. The winter is almost over and
>> I need to switch to other activities like earning money.
>
> Understood.
>
>> I understand. I didn't know there was a rewrite. I'm not into Python, but
>> if you could post a link, I'd take a look out of curiosity.
>>
>> If the community prefers Python, what can I say about this? Their choice.
>
> This is the kernel community you're talking about - saying that it
> prefers any language (except possibly C) is asking for big-time trouble
> :)
>
> *I* prefer Python, and the Sphinx side of things is necessarily in
> Python, so I'd be happy to see kernel-doc move over. That said, others
> certainly disagree.
>
> Markus's work was here:
>
> https://lore.kernel.org/lkml/1485287564-24205-1-git-send-email-markus.heiser@darmarit.de/
I can barely modify Python script, but I think that this would be a good move overall.
Then I could learn more Python.
> At the time, we were just trying to get the RST transition done, and
> swapping out the kernel-doc script seemed like a major distraction that
> we didn't need, so this never got looked at as seriously as I would have
> liked.
>
>> Personally, I'd rather play with translating this script to Raku (aka
>> Perl 6).
>
> Trying to add yet another language dependency is another path to
> unhappiness, we're not going to go there.
--
~Randy
next prev parent reply other threads:[~2022-02-17 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 22:39 [RFC] scripts: kernel-doc: Major kernel-doc rework Tomasz Warniełło
2022-02-15 23:51 ` Jonathan Corbet
2022-02-16 23:45 ` Jonathan Corbet
2022-02-17 15:32 ` Tomasz Warniełło
2022-02-17 17:04 ` Jonathan Corbet
2022-02-17 17:50 ` Randy Dunlap [this message]
2022-02-18 2:29 ` Tomasz Warniełło
2022-02-18 3:07 ` Matthew Wilcox
2022-02-21 12:57 ` Jani Nikula
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=f30311b5-1b30-ed79-ca66-4359a8f9586b@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomasz.warniello@gmail.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;
as well as URLs for NNTP newsgroup(s).