From: "Sven Eden" <sven.eden@gmx.de>
To: cygwin@cygwin.com
Subject: Aw: Re: Re: Problematic interpretion of paths starting with double slashes
Date: Wed, 13 Jun 2018 13:05:00 -0000 [thread overview]
Message-ID: <trinity-793945e5-5231-40f5-b016-dde0d58b3f16-1528883857891@3c-app-gmx-bs06> (raw)
In-Reply-To: <CAD8GWssVFrh_GkLy80CfjDuwMTAS03V+qijzVZcX0Eh7df9VTw@mail.gmail.com>
> Gesendet: Dienstag, 12. Juni 2018 um 20:02 Uhr
> Von: Lee <ler762@gmail.com>
> On 6/12/18, Sven Eden wrote:
> > Good style is to guarantee, that
> > not more than one slash is issued.
>
> Why don't you submit a patch to guarantee that not more than one slash
> is issued?
Already done.
> Or submit a bug report that the earlier patch broke portability?
Already done.
> Asking cygwin to change their long standing, posix allowed,
> implementation defined behavior seems like the least likely way to get
> the problem fixed.
I never did that. All I did was to ask whether such an
extension would be possible.
It is, so my question is answered.
And btw., the implementation, if extended in the way I
proposed, would still be POSIX compliant. ;-)
Cheers
Sven
--
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-13 9:57 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 ` Sven Eden [this message]
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=trinity-793945e5-5231-40f5-b016-dde0d58b3f16-1528883857891@3c-app-gmx-bs06 \
--to=sven.eden@gmx.de \
--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).