From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: glibc 2.34 - Hard ABI freeze effective immediately.
Date: Mon, 19 Jul 2021 11:13:19 -0300 [thread overview]
Message-ID: <dbe17961-90de-3d30-619e-261809e1f90f@linaro.org> (raw)
In-Reply-To: <874kcqxvgs.fsf@oldenburg.str.redhat.com>
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.
next prev parent reply other threads:[~2021-07-19 14:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 2:43 glibc 2.34 - Slushy freeze effective immediately Carlos O'Donell via Libc-alpha
2021-07-19 2:15 ` glibc 2.34 - Hard ABI " Carlos O'Donell via Libc-alpha
2021-07-19 13:51 ` Florian Weimer via Libc-alpha
2021-07-19 14:13 ` Adhemerval Zanella via Libc-alpha [this message]
2021-07-19 14:30 ` Florian Weimer via Libc-alpha
2021-07-22 12:28 ` Carlos O'Donell via Libc-alpha
2021-07-22 13:02 ` Carlos O'Donell via Libc-alpha
2021-07-22 17:56 ` Florian Weimer via Libc-alpha
2021-07-22 12:31 ` Carlos O'Donell via Libc-alpha
2021-07-22 13:24 ` Adhemerval Zanella via Libc-alpha
2021-07-23 5:13 ` Carlos O'Donell via Libc-alpha
2021-07-23 5:53 ` Siddhesh Poyarekar via Libc-alpha
2021-07-26 14:22 ` Carlos O'Donell via Libc-alpha
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 via Libc-alpha
2021-07-26 13:00 ` Carlos O'Donell via Libc-alpha
2021-07-26 13:13 ` Adhemerval Zanella via Libc-alpha
2021-07-26 18:31 ` Adhemerval Zanella via Libc-alpha
2021-07-22 13:51 ` Siddhesh Poyarekar
2021-07-25 19:46 ` H.J. Lu via Libc-alpha
2021-07-25 21:54 ` Florian Weimer via Libc-alpha
2021-07-25 22:07 ` H.J. Lu via Libc-alpha
2021-07-25 22:14 ` Florian Weimer via Libc-alpha
2021-07-26 7:19 ` Andreas Schwab
2021-07-26 14:29 ` Carlos O'Donell via Libc-alpha
2021-07-26 14:32 ` H.J. Lu via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbe17961-90de-3d30-619e-261809e1f90f@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@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).