From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Samuel Thibault <samuel.thibault@aquilenet.fr>,
Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha <libc-alpha@sourceware.org>,
Siddhesh Poyarekar <siddhesh@redhat.com>
Subject: Re: glibc 2.34 - Hard ABI freeze effective immediately.
Date: Mon, 26 Jul 2021 20:07:25 +0530 [thread overview]
Message-ID: <0736bf68-9bef-de61-4ea8-a8289691dc23@gotplt.org> (raw)
In-Reply-To: <20210726142802.vch7zfiovnztiing@begin>
On 7/26/21 7:58 PM, Samuel Thibault wrote:
>> I want to minimize the number of changes we make this week.
>>
>> If they can wait until glibc 2.35 opens then I think they should.
>
> The build fix for hurd is very trivial, and needed to be able to get
> make check
> to produce an actual output.
I already pushed it, I think Carlos was referring to the remaining fixes
that haven't yet been reviewed.
Siddhesh
next prev parent reply other threads:[~2021-07-26 14:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 2:43 glibc 2.34 - Slushy " Carlos O'Donell
2021-07-19 2:15 ` glibc 2.34 - Hard ABI " Carlos O'Donell
2021-07-19 13:51 ` Florian Weimer
2021-07-19 14:13 ` Adhemerval Zanella
2021-07-19 14:30 ` Florian Weimer
2021-07-22 12:28 ` Carlos O'Donell
2021-07-22 13:02 ` Carlos O'Donell
2021-07-22 17:56 ` Florian Weimer
2021-07-22 12:31 ` Carlos O'Donell
2021-07-22 13:24 ` Adhemerval Zanella
2021-07-23 5:13 ` Carlos O'Donell
2021-07-23 5:53 ` Siddhesh Poyarekar
2021-07-26 14:22 ` Carlos O'Donell
2021-07-26 14:28 ` Samuel Thibault
2021-07-26 14:37 ` Siddhesh Poyarekar [this message]
2021-07-26 14:45 ` Samuel Thibault
2021-07-23 13:13 ` Adhemerval Zanella
2021-07-26 13:00 ` Carlos O'Donell
2021-07-26 13:13 ` Adhemerval Zanella
2021-07-26 18:31 ` Adhemerval Zanella
2021-07-22 13:51 ` Siddhesh Poyarekar
2021-07-25 19:46 ` H.J. Lu
2021-07-25 21:54 ` Florian Weimer
2021-07-25 22:07 ` H.J. Lu
2021-07-25 22:14 ` Florian Weimer
2021-07-26 7:19 ` Andreas Schwab
2021-07-26 14:29 ` Carlos O'Donell
2021-07-26 14:32 ` H.J. Lu
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=0736bf68-9bef-de61-4ea8-a8289691dc23@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=samuel.thibault@aquilenet.fr \
--cc=siddhesh@redhat.com \
/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).