From: u-igbb@aetey.se
To: musl@lists.openwall.com
Subject: Re: RFC 3484 goals: partial or full coverage?
Date: Tue, 3 Jun 2014 10:15:58 +0200 [thread overview]
Message-ID: <20140603081558.GL31947@example.net> (raw)
In-Reply-To: <20140603032909.GA4505@brightrain.aerifal.cx>
On Mon, Jun 02, 2014 at 11:29:09PM -0400, Rich Felker wrote:
> Ideally I'd like to avoid adding more than ~500 bytes of code size to
> libc (and static binaries using it) to make this stuff work, and I
> certainly don't want to add runtime costs that are unreasonable to
> many users. But choosing whether to return v4 or v6 results first
> (this is one of the most visible effects of the whole procedure) seems
> pretty important from a sense of not pessimizing systems that have
> both v4 and v6 but where using one is much worse than the other.
+1
Rune
prev parent reply other threads:[~2014-06-03 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 3:29 Rich Felker
2014-06-03 8:15 ` u-igbb [this message]
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=20140603081558.GL31947@example.net \
--to=u-igbb@aetey.se \
--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).