DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=XdlTX5k
	0H6l0aszTT6MQHZMIWHSRIuiaC/n3YbPZ5bdHw4u8qf9ej+hpXolpeVJfu8atvaH
	76qURycAlfUC+BT32IXVR60/PKuxnAXOAOQwwrvsQ2V+vcSrAhBIaXM1BIRtJefh
	88Gt5bXu3EJzTd25Yj/H3KZvCSUg/k2UcdQE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <trinity-2aa37c55-032a-4631-9d8f-657ecd85e170-1528809265158@3c-app-gmx-bs08>
References: <trinity-82173dac-d842-4a87-8d1f-bed9a958d178-1528793630066@3c-app-gmx-bs08> <dc8418d2-2004-97f0-2d8c-ab438f007eba@redhat.com> <trinity-2aa37c55-032a-4631-9d8f-657ecd85e170-1528809265158@3c-app-gmx-bs08>
From: Lee <ler762@gmail.com>
Date: Tue, 12 Jun 2018 14:02:16 -0400
Message-ID: <CAD8GWssVFrh_GkLy80CfjDuwMTAS03V+qijzVZcX0Eh7df9VTw@mail.gmail.com>
Subject: Re: Re: Problematic interpretion of paths starting with double slashes
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On 6/12/18, Sven Eden  wrote:
>> Gesendet: Dienstag, 12. Juni 2018 um 13:52 Uhr Von: "Eric Blake"
>> Then fix your script to provide 3 slashes instead of 2. Only 2 slashes
>> has the magic UNC behavior.
>
> It is not my script. *my* scripts are portable by all means.
>
>> That is, if you have a script that is concatenating:
>>
>> ${prefix}/${dir}
>>
>> where ${prefix} might be empty, you can always rewrite it to be:
>>
>> ${prefix}///${dir}
>
> The script was "fixed" from ${prefix}/${dir} a while ago.
> Before that the outcome was "///".
>
> Which is very bad style.

but it was portable

> 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?
Or submit a bug report that the earlier patch broke portability?

Asking cygwin to change their long standing, posix allowed,
implementation defined behavior seems like the least likely way to get
the problem fixed.

Regards,
Lee

--
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