From: Joseph Myers <joseph@codesourcery.com>
To: <libc-alpha@sourceware.org>
Subject: Ping Re: Make endian-conversion macros always return correct types (bug 16458)
Date: Wed, 11 Jan 2017 14:12:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1701111406040.15694@digraph.polyomino.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1701100340230.8116@digraph.polyomino.org.uk>
Ping (rather soon, but the longer we leave the build broken the more
likely it is that new build failures appear before the old ones are fixed
and it's hard to disentangle the causes; glibc may be in a freeze, but GCC
and binutils development are pretty active right now). This patch
<https://sourceware.org/ml/libc-alpha/2017-01/msg00151.html> is pending
review.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-01-11 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 3:43 Joseph Myers
2017-01-11 14:12 ` Joseph Myers [this message]
2017-01-11 14:28 ` Siddhesh Poyarekar
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=alpine.DEB.2.20.1701111406040.15694@digraph.polyomino.org.uk \
--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).