From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Aurelien Jarno <aurelien@aurel32.net>, libc-alpha@sourceware.org
Cc: Carlos O'Donell <carlos@redhat.com>, libc-stable@sourceware.org
Subject: Re: [PATCH] GLIBC-SA-2024-0004: add commit for 2.31 branch
Date: Wed, 24 Apr 2024 09:36:19 -0300 [thread overview]
Message-ID: <fad0b94c-5b51-44f9-84b1-211d02a3ecea@linaro.org> (raw)
In-Reply-To: <20240422220554.3502687-1-aurelien@aurel32.net>
LGTM, thanks. As a side note, we only have Carlos marked as interested
on this release [1], and that's why I have not initially backported this
fix on 2.31. It would be good to add yourself on the list for future
reference.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
[1] https://sourceware.org/glibc/wiki/Release/2.31
On 22/04/24 19:05, Aurelien Jarno wrote:
> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
> ---
> advisories/GLIBC-SA-2024-0004 | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/advisories/GLIBC-SA-2024-0004 b/advisories/GLIBC-SA-2024-0004
> index 23a8115d63..08df2b3118 100644
> --- a/advisories/GLIBC-SA-2024-0004
> +++ b/advisories/GLIBC-SA-2024-0004
> @@ -23,5 +23,6 @@ Fix-Commit: 36280d1ce5e245aabefb877fe4d3c6cff95dabfa (2.35-315)
> Fix-Commit: a8b0561db4b9847ebfbfec20075697d5492a363c (2.34-459)
> Fix-Commit: ed4f16ff6bed3037266f1fa682ebd32a18fce29c (2.33-263)
> Fix-Commit: 682ad4c8623e611a971839990ceef00346289cc9 (2.32-140)
> +Fix-Commit: 3703c32a8d304c1ee12126134ce69be965f38000 (2.31-154)
>
> Reported-By: Charles Fol
next prev parent reply other threads:[~2024-04-24 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 22:05 Aurelien Jarno
2024-04-24 12:36 ` Adhemerval Zanella Netto [this message]
2024-04-24 22:25 ` Aurelien Jarno
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=fad0b94c-5b51-44f9-84b1-211d02a3ecea@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=aurelien@aurel32.net \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@sourceware.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).