From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Problematic interpretion of paths starting with double slashes
Date: Fri, 15 Jun 2018 02:41:00 -0000 [thread overview]
Message-ID: <5b7147ce-774d-f034-ac40-c368aa1cab9f@SystematicSw.ab.ca> (raw)
In-Reply-To: <trinity-709441a4-b53d-4bbd-96fb-91ad85816938-1528878894364@3c-app-gmx-bs06>
On 2018-06-13 02:34, Sven Eden wrote:
> However, from my two questions, one was answered, and I can
> figure out the other just fine by myself.
> Q: Can the handling of // be extended to check for / if the
> first fails?
> A: Yes
> Unanswered: Is the relevant stuff to be found in winsup/cygwin?
Look at:
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=blob_plain;f=winsup/cygwin/fhandler_netdrive.cc;hb=HEAD
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-14 17:41 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 [this message]
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
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=5b7147ce-774d-f034-ac40-c368aa1cab9f@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).