From: Laurent Bercot <ska-dietlibc@skarnet.org>
To: musl@lists.openwall.com
Subject: Re: Re: Resolver overhaul concepts
Date: Sat, 10 May 2014 10:26:46 +0100 [thread overview]
Message-ID: <536DF0D6.3030405@skarnet.org> (raw)
In-Reply-To: <20140510023653.GN26358@brightrain.aerifal.cx>
On 10/05/2014 03:36, Rich Felker wrote:
> doesn't let you do anything you can't already do with AF_INET[6] and
> udp.
Nit: it does. (User authentication, fd passing.) But I agree that
this is not needed for name resolution and would gratuitously add
muslisms.
--
Laurent
next prev parent reply other threads:[~2014-05-10 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 12:42 Rich Felker
2014-05-04 16:07 ` Laurent Bercot
2014-05-04 16:24 ` Rich Felker
2014-05-04 17:56 ` Laurent Bercot
2014-05-04 19:04 ` Rich Felker
2014-05-04 21:32 ` Laurent Bercot
2014-05-10 1:04 ` Andy Lutomirski
2014-05-10 2:36 ` Rich Felker
2014-05-10 9:26 ` Laurent Bercot [this message]
2014-05-10 17:41 ` Rich Felker
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=536DF0D6.3030405@skarnet.org \
--to=ska-dietlibc@skarnet.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).