From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/1] Recognizing native Windows AF_UNIX sockets
Date: Mon, 1 Feb 2021 10:54:58 +0100 [thread overview]
Message-ID: <20210201095458.GG375565@calimero.vinschen.de> (raw)
In-Reply-To: <20210130163436.21257-1-kbrown@cornell.edu>
On Jan 30 11:34, Ken Brown via Cygwin-patches wrote:
> This patch attempts to fix the problem reported here:
>
> https://cygwin.com/pipermail/cygwin/2020-September/246362.html
>
> See also the followup here:
>
> https://cygwin.com/pipermail/cygwin/2021-January/247666.html
>
> The problem, briefly, is that on certain recent versions of Windows
> 10, including 2004 but not 1909, native Windows AF_UNIX sockets are
> represented by reparse points that Cygwin doesn't recognize. As a
> result, tools like 'ls' and 'rm' don't work.
LGTM, please push.
Thanks,
Corinna
prev parent reply other threads:[~2021-02-01 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 16:34 Ken Brown
2021-01-30 16:34 ` [PATCH 1/1] Cygwin: recognize native Windows AF_UNIX sockets as reparse points Ken Brown
2021-01-30 20:58 ` [PATCH 0/1] Recognizing native Windows AF_UNIX sockets Ken Brown
2021-02-01 9:54 ` Corinna Vinschen [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=20210201095458.GG375565@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).