All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: Carlos O'Donell <carlos@redhat.com>,  linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/sigaction.2: Update si_code list with Linux v6.16
Date: Tue, 09 Sep 2025 16:15:09 -0300	[thread overview]
Message-ID: <87a533a14y.fsf@linaro.org> (raw)
In-Reply-To: <jjyin6xofibfjxs46dkhb7jg274tmhpyf37nu77fcuutglv63j@2l6bbcqdyjih> (Alejandro Colomar's message of "Tue, 9 Sep 2025 20:58:29 +0200")

Alejandro Colomar <alx@kernel.org> writes:

> Hi Carlos,
>
> On Tue, Sep 09, 2025 at 02:26:10PM -0400, Carlos O'Donell wrote:
>> > So, all the things that Carlos said weren't in glibc are now in glibc?
>> 
>> Yes. https://sourceware.org/cgit/glibc/commit/?id=6f120faf649f03a261e3e64d5b5991030383c1b3
>
> Thanks!
>
>> > Would you mind adding "(since glibc X.Y)" to them in the patch?
>> 
>> You could write "(since glibc 2.43)" though it won't be released until 2026-02-01.
>
> Yep, that will work.  We can fix the page if the final version number
> ends up being different.

Thanks I just sent a v2 with that change, and also a fix to use .BR
where .B was used incorrectly in v1.
-- 
Thiago

      reply	other threads:[~2025-09-09 19:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-28 21:07 [PATCH] man/man2/sigaction.2: Update si_code list with Linux v6.16 Thiago Jung Bauermann
2025-08-29 11:56 ` Carlos O'Donell
2025-09-03  3:08   ` Thiago Jung Bauermann
2025-09-03 15:37     ` Carlos O'Donell
2025-09-09  3:13       ` Thiago Jung Bauermann
2025-09-09  6:32         ` Alejandro Colomar
2025-09-09 18:26           ` Carlos O'Donell
2025-09-09 18:58             ` Alejandro Colomar
2025-09-09 19:15               ` Thiago Jung Bauermann [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=87a533a14y.fsf@linaro.org \
    --to=thiago.bauermann@linaro.org \
    --cc=alx@kernel.org \
    --cc=carlos@redhat.com \
    --cc=linux-man@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.