Linux io-uring development
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	io-uring Mailing List <io-uring@vger.kernel.org>
Subject: Re: [RFC PATCH liburing] man: Convert manpages to markdown
Date: Fri, 19 Jun 2026 13:05:52 -0400	[thread overview]
Message-ID: <87eci2pij3.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <4217902f-5b99-4592-aeea-9ac3804da325@gnuweeb.org>

Ammar Faizi <ammarfaizi2@gnuweeb.org> writes:

> On 6/19/26 6:05 AM, Gabriel Krisman Bertazi wrote:
>> This has been discussed for a while due to the ongoing pain of writing
>> groff.  Now that we just had a release, convert the manpages to markdown
>> and add infrastructure to generate back the groff automatically during
>> compilation.
>
> Wow, big changes:
>
>    399 files changed, 11719 insertions(+), 18975 deletions(-)
>
> Yeah, I agree that writing in GNU roff is more painful than writing in
> markdown. Interesting patch.

Yeah, this is gonna be shitty to review.  The conversion was done
mostly automatically though, you can review Makefile for that.

I'll split it up into manageable chunks.

>
> Can we also word-wrap the markdown files? It's easier to read them in
> raw if they're word-wrapped as well.

Let me see if I can get the right pandoc incantation.

-- 
Gabriel Krisman Bertazi

      reply	other threads:[~2026-06-19 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 23:05 [RFC PATCH liburing] man: Convert manpages to markdown Gabriel Krisman Bertazi
2026-06-18 23:53 ` Ammar Faizi
2026-06-19 17:05   ` Gabriel Krisman Bertazi [this message]

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=87eci2pij3.fsf@mailhost.krisman.be \
    --to=krisman@suse.de \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.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