From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Fangrui Song via Libc-alpha <libc-alpha@sourceware.org>
Cc: Cary Coutant <ccoutant@gmail.com>
Subject: Re: [PATCH] elf.h: Add ELFCOMPRESS_ZSTD
Date: Mon, 18 Jul 2022 10:01:21 -0400 [thread overview]
Message-ID: <bddde8b3-54fe-ac80-1b15-640399da5d55@redhat.com> (raw)
In-Reply-To: <871qus8cuw.fsf@oldenburg.str.redhat.com>
On 7/11/22 00:58, Florian Weimer via Libc-alpha wrote:
> * Fangrui Song via Libc-alpha:
>
>> I wish that the macro definition can catch up the upcoming
>> https://sourceware.org/glibc/wiki/Release/2.36 [1], so that
>> projects can expect the value ELFCOMPRESS_ZSTD from elf.h.
>> The projects may choose to define the macro themselves,
>> but having the definition in an earlier release seems a good idea
>> anyway, and it the glibc definition makes it clearer ELFCOMPRESS_ZSTD
>> is standard and vendors can start adding support.
>>
>> [1]: https://sourceware.org/pipermail/libc-alpha/2022-July/140352.html
>> ("Release of glibc 2.36 in 1 month! Please add blockers and desirable for release.")
>
> This looks quite backportable to me, so it should not be a release
> blocker. It's only a blocker if we apply the patch today, then we'd
> have to wait until the gABI assignment actually happens as expected.
Agreed. This is a NACK from me as the RM until the gABI assignment happens.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2022-07-18 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 23:32 Fangrui Song
2022-07-11 4:58 ` Florian Weimer
2022-07-18 14:01 ` Carlos O'Donell [this message]
2022-07-22 23:08 ` Fangrui Song
2022-07-26 20:23 ` Adhemerval Zanella Netto
2022-07-26 20:30 ` Fangrui Song
2022-07-29 15:44 ` Carlos O'Donell
2022-08-04 20:04 ` Fangrui Song
2022-08-10 7:09 ` Fangrui Song
2022-08-10 7:46 ` Florian Weimer
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=bddde8b3-54fe-ac80-1b15-640399da5d55@redhat.com \
--to=carlos@redhat.com \
--cc=ccoutant@gmail.com \
--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).