From: Tom Kacvinsky <tkacvins@gmail.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH glibc/release/2.38/master] elf: Remove l_init_called_next field from struct link_map
Date: Wed, 24 Apr 2024 10:39:21 -0400 [thread overview]
Message-ID: <90DFBECA-9825-40DB-AA4A-AC5BCBBA53D0@gmail.com> (raw)
In-Reply-To: <e6109494-0871-4a6f-900c-ce5b31b64615@linaro.org>
> Please refrain to add this footnote on email intended for public maillist,
> usually this make the message being solely ignored
Some people don’t have a choice in the matter. Their employer automatically adds the boilerplate text. That’s why I started using my personal email account for public mailing lists.
next prev parent reply other threads:[~2024-04-24 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 3:44 Mark Zhuang
2024-04-24 12:33 ` Adhemerval Zanella Netto
2024-04-24 14:23 ` Florian Weimer
2024-04-24 14:39 ` Tom Kacvinsky [this message]
2024-04-24 15:47 mark.zhuang
2024-04-29 14:58 ` Mark Zhuang
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=90DFBECA-9825-40DB-AA4A-AC5BCBBA53D0@gmail.com \
--to=tkacvins@gmail.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).