public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/18532] New: gethostbyaddr in6addr_any, in6addr_loopback namespace
Date: Sun, 14 Jun 2015 14:19:00 -0000 [thread overview]
Message-ID: <bug-18532-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18532
Bug ID: 18532
Summary: gethostbyaddr in6addr_any, in6addr_loopback namespace
Product: glibc
Version: 2.21
Status: NEW
Severity: normal
Priority: P2
Component: network
Assignee: unassigned at sourceware dot org
Reporter: jsm28 at gcc dot gnu.org
Target Milestone: ---
gethostbyaddr brings in references to in6addr_any and thereby in6addr_loopback,
which aren't in all the standards containing gethostbyaddr (gethostbyaddr is in
XPG4 and UNIX98, in6addr_any and in6addr_loopback are new in POSIX.1:2001).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-06-14 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 14:19 jsm28 at gcc dot gnu.org [this message]
2015-06-14 14:33 ` [Bug network/18532] " cvs-commit at gcc dot gnu.org
2015-06-17 20:09 ` cvs-commit at gcc dot gnu.org
2015-06-17 20:23 ` jsm28 at gcc dot gnu.org
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=bug-18532-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).