From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Aw: Re: Problematic interpretion of paths starting with double slashes
Date: Wed, 13 Jun 2018 09:57:00 -0000 [thread overview]
Message-ID: <20180613080953.GR7851@calimero.vinschen.de> (raw)
In-Reply-To: <87efhbdbaz.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Jun 12 22:01, Achim Gratz wrote:
> Sven Eden writes:
> > Doing a simple stat on / if (and only if) the UNC lookup
> > fails, does not endanger anything. It wouldn't break
> > anything or do any other damage. Besides from adding an
> > additional <0.01s lag to any failed access that *really*
> > meant a network share.
> >
> > So no. Adding this tiny extra functionality wouldn't break
> > anything for anybody, but allowed the usage of software that
> > relies on the non-cygwin behaviour. (And is outside the
> > users control.)
>
> Well, it does break things if both
>
> //this/or/that
> /this/or/that
>
> exist and then at some point host "this" becomes unreachable. So I'd
> keep //unc/path to mean just that on principle.
ACK
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-13 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 11:45 Sven Eden
2018-06-12 11:52 ` Adam Dinwoodie
2018-06-12 16:28 ` Eric Blake
2018-06-12 17:12 ` Aw: " Sven Eden
2018-06-12 17:57 ` Brian Inglis
2018-06-13 10:14 ` Aw: " Sven Eden
2018-06-13 13:49 ` Andrey Repin
2018-06-15 2:41 ` Brian Inglis
2018-06-12 20:01 ` Aw: " Eric Blake
2018-06-13 13:05 ` Sven Eden
2018-06-12 20:32 ` Lee
2018-06-13 13:05 ` Aw: " Sven Eden
2018-06-12 23:31 ` Aw: " Achim Gratz
2018-06-13 9:57 ` Corinna Vinschen [this message]
2018-06-13 13:29 ` Sven Eden
2018-06-13 19:32 ` Achim Gratz
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=20180613080953.GR7851@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).