From: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: fweimer@redhat.com, gcc@gcc.gnu.org, ville.voutilainen@gmail.com,
linux-man@vger.kernel.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org, libstdc++@gcc.gnu.org,
libc-coord@lists.openwall.com, libc-alpha@sourceware.org,
jwakely@redhat.com, enh@google.com
Subject: Re: Ping(3): [PATCH v4] <sys/param.h>: Add nitems()
Date: Tue, 17 Nov 2020 23:59:51 +0100 [thread overview]
Message-ID: <8fb9c722-4190-6115-1d60-d94f8db7f749@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2011172242582.28480@digraph.polyomino.org.uk>
Hi Joseph,
On 11/17/20 11:44 PM, Joseph Myers wrote:
> I've asked the WG14 reflector why N2529 (and N2530, though that one's not
> relevant to this feature) doesn't seem to have made it onto a meeting
> agenda yet, when there have been two WG14 meetings since that proposal
was
> made and a third one coming up.
>
Nice!
Please update me on any feedback you receive.
So glibc will basically hold this patch
at least until the WG answers to that, right?
Thanks,
Alex
next prev parent reply other threads:[~2020-11-17 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:12 [PATCH v4] <sys/param.h>: Add nitems() Alejandro Colomar via Libc-alpha
2020-10-11 16:43 ` Ping: " Alejandro Colomar via Libc-alpha
2020-10-27 11:38 ` Ping(2): " Alejandro Colomar via Libc-alpha
2020-11-17 22:23 ` Ping(3): " Alejandro Colomar via Libc-alpha
2020-11-17 22:44 ` Joseph Myers
2020-11-17 22:59 ` Alejandro Colomar via Libc-alpha [this message]
2020-11-17 23:11 ` Joseph Myers
2020-11-18 11:26 ` Alejandro Colomar via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8fb9c722-4190-6115-1d60-d94f8db7f749@gmail.com \
--to=libc-alpha@sourceware.org \
--cc=colomar.6.4.3@gmail.com \
--cc=enh@google.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.com \
--cc=libc-coord@lists.openwall.com \
--cc=libstdc++@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=ville.voutilainen@gmail.com \
/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).