From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: glibc 2.34 - Hard ABI freeze effective immediately.
Date: Thu, 22 Jul 2021 09:02:54 -0400 [thread overview]
Message-ID: <0d610631-cd89-eea0-fbfc-828fe6682908@redhat.com> (raw)
In-Reply-To: <b9beb4ee-0fe4-b4b0-c74e-1882dc2bd801@redhat.com>
On 7/22/21 8:28 AM, Carlos O'Donell wrote:
> On 7/19/21 10:30 AM, Florian Weimer via Libc-alpha wrote:
>> * Adhemerval Zanella:
>>
>>> On 19/07/2021 10:51, Florian Weimer via Libc-alpha wrote:
>>>> * Carlos O'Donell via Libc-alpha:
>>>>
>>>>> On 7/4/21 10:43 PM, Carlos O'Donell wrote:
>>>>>> We are in slushy freeze right now. I'm reviewing the last of the ABI
>>>>>> changes we want to make in glibc 2.34.
>>>>>
>>>>> The ABI freeze is now hard freeze, I would like to avoid any further ABI
>>>>> changes that are not on this list.
>>>>>
>>>>> If you have an ABI change please reach and respond to this thread
>>>>> immediately with the request.
>>>>
>>>> I suggest to add __ioctl_time64 and related functions on 32-bit, for
>>>> future-proofing the time64 ABI:
>>>>
>>>> Additional time64 aliases
>>>> <https://sourceware.org/pipermail/libc-alpha/2021-July/128485.html>
>>>
>>> I will review these.
>>
>> Thanks. I need to repost it because of several conflicts.
>
> This is now complete, we have time64 aliases so this part of the ABI is now frozen.
Actually, turns out I'm wrong, we need a few more hours for this.
We'll be frozen soon.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-07-22 13:02 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 [this message]
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
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=0d610631-cd89-eea0-fbfc-828fe6682908@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).