public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: axboe@kernel.dk,  io-uring@vger.kernel.org,  ammarfaizi2@gnuweeb.org
Subject: Re: [PATCH liburing 0/3] Convert manpages to markdown
Date: Fri, 10 Jul 2026 08:14:41 -0400	[thread overview]
Message-ID: <x498q7jf3da.fsf@segfault.usersys.redhat.com> (raw)
In-Reply-To: <87zf028ng8.fsf@mailhost.krisman.be> (Gabriel Krisman Bertazi's message of "Tue, 07 Jul 2026 18:05:59 -0400")

Gabriel Krisman Bertazi <krisman@suse.de> writes:

> Jeff Moyer <jmoyer@redhat.com> writes:
>
>> I don't have a strong opinion.  Either way, I'll be looking at
>> documentation and/or prior examples to make the changes I need to make.
>> :)  As I said in my last follow-up, it would be enough for me if the
>> generated man pages were simply part of the release tarballs (it's not
>> necessary to check them into git).  I'm sure that can be accomplished
>> with makefile magic.
>
> I considered that, part of a 'make dist'-kind of rule.  But
> there is the tarballs generated by github which do a simple
> git-archive. I don't think we can change them to run a custom command.
>
> We fetch our sources from https://brick.kernel.dk.  That seems to be
> generated by the create-archive rule, which we could patch.
>
> If github tarballs differing from Jens' server are not a problem, and
> you can use that server, I'm happy make it build through the
> create-archive rule.  Should solve the problem.

Yes, I use brick.kernel.dk.

>>>> At the very least, please make generation of the man pages optional
>>>> via configure.
>>
>> And this would be a necessary part of the solution, were things to go
>> that way.
>
> ack!

Thanks, Gabriel!

-Jeff


      reply	other threads:[~2026-07-10 12:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 21:41 [PATCH liburing 0/3] Convert manpages to markdown Gabriel Krisman Bertazi
2026-07-06 21:41 ` [PATCH liburing 1/3] man: Generate aliases during compilation Gabriel Krisman Bertazi
2026-07-06 21:41 ` [PATCH liburing 2/3] man: Introduce rules to convert Markdown to groff Gabriel Krisman Bertazi
2026-07-06 21:41 ` [PATCH liburing 3/3] man: Convert manpages to markdown Gabriel Krisman Bertazi
2026-07-07 12:27 ` [PATCH liburing 0/3] " Jeff Moyer
2026-07-07 14:56   ` Jeff Moyer
2026-07-07 15:20   ` Gabriel Krisman Bertazi
2026-07-07 18:12     ` Jeff Moyer
2026-07-07 22:05       ` Gabriel Krisman Bertazi
2026-07-10 12:14         ` Jeff Moyer [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=x498q7jf3da.fsf@segfault.usersys.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=krisman@suse.de \
    /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