public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tore at fud dot no" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug network/14413] nsswitch doesn't implement getaddrinfo(), plugins cannot provide full getaddrinfo features
Date: Tue, 31 Jul 2012 18:43:00 -0000 [thread overview]
Message-ID: <bug-14413-131-kR07y4nTvt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14413-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14413
Tore Anderson <tore at fud dot no> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tore at fud dot no
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-07-31 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:13 [Bug network/14413] New: nsswitch doesn't implement getaddrinfo(), plugins cannot supply link-local IPv6 addresses with scope id psimerda at redhat dot com
2012-07-27 15:16 ` [Bug network/14413] " psimerda at redhat dot com
2012-07-31 13:28 ` [Bug network/14413] nsswitch doesn't implement getaddrinfo(), plugins cannot provide full getaddrinfo features psimerda at redhat dot com
2012-07-31 13:31 ` psimerda at redhat dot com
2012-07-31 18:43 ` tore at fud dot no [this message]
2014-06-02 3:32 ` aoliva at sourceware dot org
2014-06-02 8:32 ` psimerda at redhat dot com
2014-06-17 18:53 ` fweimer at redhat dot com
2014-12-30 22:22 ` psimerda at redhat dot com
2020-04-07 19:53 ` gavin at matician dot com
2021-12-01 15:10 ` sam at gentoo dot org
2023-03-21 9:49 ` matthijsvanduin at gmail dot com
2023-03-22 3:17 ` sam at gentoo dot 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-14413-131-kR07y4nTvt@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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).