From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Problems with getifaddrs
Date: Thu, 29 Jul 2021 10:43:00 -0400 [thread overview]
Message-ID: <830e9b62-a002-1a67-5c83-96204f570d9e@cornell.edu> (raw)
In-Reply-To: <529122968.20210727020408@yandex.ru>
On 7/26/2021 7:04 PM, Andrey Repin wrote:
> There's actually no IP address assigned to TAP55, which could be reported as 0/0.
Follow-up for the sake of the archives: The question I raised is whether
getifaddrs *should* report an IP address of 0/0 in this case. After checking
what happens on Linux, Corinna agreed that it should not do this, and we've now
changed it:
https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=b88d686a68d7bf2ff22d857a28d37fe4fdbafdf2
Ken
prev parent reply other threads:[~2021-07-29 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 15:15 Ken Brown
2021-07-26 23:04 ` Andrey Repin
2021-07-29 14:43 ` Ken Brown [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=830e9b62-a002-1a67-5c83-96204f570d9e@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.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).