mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <>
To: Fangrui Song <>
Cc:, Cary Coutant <>
Subject: Re: [musl] [PATCH] elf.h: add ELFCOMPRESS_ZSTD
Date: Wed, 3 Aug 2022 12:00:09 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

* Fangrui Song <> [2022-08-02 13:01:26 -0700]:
> On 2022-08-02, Rich Felker wrote:
> > 
> > Is this actually an adopted standard? It's not clear from the link
> > above whether there's anything authoritative going on or a proposal
> > that some people like.
> I think so, from Cary's
> "I will add this to the ELF spec, as proposed below:".

i think at this point the closest to a single point of truth for
the elf spec is cary's approval mails on the generic abi list.

      parent reply	other threads:[~2022-08-03 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  2:14 Fangrui Song
2022-08-02 17:55 ` Rich Felker
2022-08-02 20:01   ` Fangrui Song
2022-08-02 23:09     ` Cary Coutant
2022-08-03 10:00     ` Szabolcs Nagy [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 NNTP newsgroup(s).