From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Andreas Schwab <schwab@suse.de>
Subject: Re: Backporting LD_AUDIT fixes to the glibc 2.34 release branch?
Date: Wed, 30 Mar 2022 11:36:59 +1300 [thread overview]
Message-ID: <CAJ8wqtd9YPDym0rAixyU6hsHxiddVZevRSUtGFe239Xt0WituQ@mail.gmail.com> (raw)
In-Reply-To: <5d39e78f-2a9f-c914-81a7-0582239f8c7e@redhat.com>
On Wed, 30 Mar 2022 at 09:46, Carlos O'Donell <carlos@redhat.com> wrote:
> Michael,
>
> Any objections?
>
2.34 is only in the non-LTS 21.10 release and I am not currently planning
to update glibc there, so no objections from me.
(I want to do a much better job than we have been doing at following the
2.35 branch for the to-be-LTS 22.04 release though!)
Cheers,
mwh
next prev parent reply other threads:[~2022-03-29 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 20:46 Carlos O'Donell
2022-03-29 21:05 ` Carlos O'Donell
2022-03-29 22:36 ` Michael Hudson-Doyle [this message]
2022-03-30 9:19 ` Andreas Schwab
2022-03-30 16:18 ` Aurelien Jarno
[not found] <mailman.20300.1648586803.2100866.libc-alpha@sourceware.org>
2022-03-31 19:58 ` John Mellor-Crummey
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=CAJ8wqtd9YPDym0rAixyU6hsHxiddVZevRSUtGFe239Xt0WituQ@mail.gmail.com \
--to=michael.hudson@canonical.com \
--cc=adhemerval.zanella@linaro.org \
--cc=aurelien@aurel32.net \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).