From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: Ping Re: Do not build sparc32 libgcc functions into static libc
Date: Wed, 13 Dec 2023 22:16:28 +0000 [thread overview]
Message-ID: <81388da3-9a11-4344-6484-55e5c8677a93@codesourcery.com> (raw)
In-Reply-To: <53dc50f-8f2b-da88-fa85-44883878201b@codesourcery.com>
Ping. This patch
<https://sourceware.org/pipermail/libc-alpha/2023-December/153227.html> is
pending review.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-12-13 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 20:11 Joseph Myers
2023-12-13 22:16 ` Joseph Myers [this message]
2023-12-19 15:54 ` Adhemerval Zanella Netto
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=81388da3-9a11-4344-6484-55e5c8677a93@codesourcery.com \
--to=joseph@codesourcery.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).