public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches <cygwin-patches@cygwin.com>
Subject: [PATCH 0/2] Fix getifaddrs problems
Date: Mon, 26 Jul 2021 17:02:44 -0400	[thread overview]
Message-ID: <4ac22273-23b7-5be4-7f4a-48f4766bfff8@cornell.edu> (raw)

The two patches in this series fix the two problems reported in

   https://cygwin.com/pipermail/cygwin/2021-July/248970.html

As I indicated in that message, I'm not 100% sure of the second patch.

Ken

Ken Brown (2):
   Cygwin: getifaddrs: fix address family for IPv6 netmasks
   Cygwin: getifaddrs: don't return a zero IPv4 address

  winsup/cygwin/net.cc | 30 ++++++++++++++++++++++++------
  1 file changed, 24 insertions(+), 6 deletions(-)

-- 
2.32.0

P.S. I'm sending the patches as attachments in the next two messages because my 
SMTP server uses an authentication method that is not compatible with git 
send-email.  If this gets to be annoying, I have a different email account that 
I could start using for patches.

             reply	other threads:[~2021-07-26 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 21:02 Ken Brown [this message]
2021-07-28  8:23 ` Corinna Vinschen

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=4ac22273-23b7-5be4-7f4a-48f4766bfff8@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-patches@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).