From: Matthew Wilcox <willy@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tomasz Warniełło" <tomasz.warniello@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] scripts: kernel-doc: Major kernel-doc rework
Date: Fri, 18 Feb 2022 03:07:06 +0000 [thread overview]
Message-ID: <Yg8NWrvooEDbKg49@casper.infradead.org> (raw)
In-Reply-To: <87bkz51l2g.fsf@meer.lwn.net>
On Thu, Feb 17, 2022 at 10:04:23AM -0700, Jonathan Corbet wrote:
> *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/
>
> 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 like to see us switch over to
https://github.com/jnikula/hawkmoth
but I don't have time to work on the rough edges. I really hate the
kernel-doc style; I think it makes us write very stilted documentation,
full of parameter descriptions like:
function() - Do the thing to a page.
@page: The page.
which really serves nobody. Being able to write:
function() - Do the thing to @page
is easier to both write and read.
next prev parent reply other threads:[~2022-02-18 3:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 22:39 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
2022-02-18 2:29 ` Tomasz Warniełło
2022-02-18 3:07 ` Matthew Wilcox [this message]
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=Yg8NWrvooEDbKg49@casper.infradead.org \
--to=willy@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
all inboxes | Powered by JetHome®