From: Andreas Schwab <schwab@linux-m68k.org>
To: Alejandro Colomar via Libc-alpha <libc-alpha@sourceware.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
Alejandro Colomar <alx.manpages@gmail.com>
Subject: Re: Rationale for inet_ntop(3) using socklen_t instead of size_t
Date: Thu, 22 Dec 2022 17:18:25 +0100 [thread overview]
Message-ID: <87a63f8l9q.fsf@igel.home> (raw)
In-Reply-To: <3b4a4b79-4f8c-1d9b-cb3b-532ddf38e057@gmail.com> (Alejandro Colomar via Libc-alpha's message of "Thu, 22 Dec 2022 13:21:08 +0100")
On Dez 22 2022, Alejandro Colomar via Libc-alpha wrote:
> P.S.: AFAIK, I can't search in the glibc mailing list history; something I
> can do in the lore.kernel.org list archives. Is it correct? Or maybe I
> just don't know how? <https://sourceware.org/pipermail/libc-alpha/>
Sourceware mailing lists are now available as public inbox, see
inbox.sourceware.org.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-12-22 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 12:21 Alejandro Colomar
2022-12-22 16:18 ` Andreas Schwab [this message]
2022-12-22 17:05 ` Alejandro Colomar
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=87a63f8l9q.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alx.manpages@gmail.com \
--cc=jakub@redhat.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).