From: Alejandro Colomar <alx@kernel.org>
To: Zack Weinberg <zack@owlfolio.org>
Cc: DJ Delorie <dj@redhat.com>, Carlos O'Donell <carlos@redhat.com>,
GNU libc development <libc-alpha@sourceware.org>
Subject: Re: [patch v4] manual: add syscall list
Date: Thu, 23 May 2024 23:18:32 +0200 [thread overview]
Message-ID: <ulpcwgccviyn5y5d6gbhuhyq42k2cmvkrtyfk6z2djbqokyezn@al3yupdo4ihd> (raw)
In-Reply-To: <b2792b30-077c-46f8-ab42-b78a28bc1d4e@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Hi Zack,
On Thu, May 23, 2024 at 12:59:13PM GMT, Zack Weinberg wrote:
> On Wed, May 22, 2024, at 3:41 PM, DJ Delorie wrote:
> > [v4 cleans up comment text and list prefixes]
>
> I saw something go by earlier about previous reviewers not being
> confident in their understanding of the changes to the configure.ac,
> so let me jump in and review that part...
That was me. :)
> > AC_DEFINE_UNQUOTED(TIMEOUTFACTOR, $timeoutfactor)
> >
> > +AC_ARG_WITH([man-pages],
> > + AS_HELP_STRING([--with-man-pages=VERSION],
> > + [tie manual to a specific man-pages version]),
> > + [man_pages_version=$withval],
> > + [man_pages_version=6.8])
> > +AC_SUBST(man_pages_version)
>
> Also, I wonder if it makes sense to tie the default here to the
> default for --enable-kernel, assuming there is one.
The versions of the Linux man-pages project are independent of the Linux
kernel ones. In fact, I think all of my releases will be 6.x, and 7.x
will be for whoever is the maintainer after me.
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-23 21:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 20:52 manual: add syscall list appendix DJ Delorie
2024-05-16 5:02 ` Florian Weimer
2024-05-16 11:44 ` Carlos O'Donell
2024-05-16 12:06 ` Florian Weimer
2024-05-16 13:37 ` Alejandro Colomar
2024-05-16 14:52 ` Carlos O'Donell
2024-05-16 15:03 ` Alejandro Colomar
2024-05-16 17:57 ` DJ Delorie
2024-05-16 17:55 ` DJ Delorie
2024-05-16 21:08 ` Alejandro Colomar
2024-05-17 13:21 ` Carlos O'Donell
2024-05-17 15:31 ` DJ Delorie
2024-05-17 19:16 ` Carlos O'Donell
2024-05-20 21:43 ` [patch v2] manual: add syscall list DJ Delorie
2024-05-20 22:10 ` Alejandro Colomar
2024-05-21 1:12 ` DJ Delorie
2024-05-21 10:22 ` Alejandro Colomar
2024-05-21 17:16 ` DJ Delorie
2024-05-21 20:04 ` [patch v3] " DJ Delorie
2024-05-22 19:07 ` Carlos O'Donell
2024-05-22 19:40 ` DJ Delorie
2024-05-22 19:41 ` [patch v4] " DJ Delorie
2024-05-22 19:42 ` DJ Delorie
2024-05-22 20:54 ` Florian Weimer
2024-05-22 21:00 ` Florian Weimer
2024-05-22 21:26 ` DJ Delorie
2024-05-23 7:31 ` Florian Weimer
2024-05-23 8:49 ` Andreas Schwab
2024-05-22 22:45 ` DJ Delorie
2024-05-22 23:12 ` Alejandro Colomar
2024-05-23 16:59 ` Zack Weinberg
2024-05-23 19:38 ` DJ Delorie
2024-05-23 19:41 ` Zack Weinberg
2024-05-23 19:46 ` DJ Delorie
2024-05-23 19:51 ` Joseph Myers
2024-05-23 21:18 ` Alejandro Colomar [this message]
2024-05-16 17:37 ` manual: add syscall list appendix DJ Delorie
2024-05-16 17:55 ` Joe Simmons-Talbott
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=ulpcwgccviyn5y5d6gbhuhyq42k2cmvkrtyfk6z2djbqokyezn@al3yupdo4ihd \
--to=alx@kernel.org \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=zack@owlfolio.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).