DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=GiHItAk2a+j5zHHB
	tfwax1ILrbhtLb+MitYxIMU4ZyZ+pkZogLqJ4F45pM8dRN70VZRLfLePcsmQhaXO
	fw0irnCCV5sDWrpPnj3o/yP8AVmsQuY9h6C3qASedd4hEKEe8zeBIpE/oQSDhe0T
	axvWsPgmZe/rnvgMiyEQrkSEzps=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 24 Oct 2014 01:50:16 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <63375991.20141024015016@yandex.ru>
To: Thomas Wolff <towo@towo.net>, cygwin@cygwin.com
Subject: Re: Problems on case-sensitive file systems
In-Reply-To: <5449390F.5000903@towo.net>
References: <54475648.3000805@towo.net> <20141022140031.GD18857@calimero.vinschen.de>   <5448F79A.6010900@towo.net> <20141023153609.GA20607@calimero.vinschen.de>  <5449390F.5000903@towo.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Thomas Wolff!

>>>>> I'm facing a number of issues with case-sensitivity which I've collected:
>>>>>
>>>>> There is a documented limitation on case-sensitivity using drive letter
>>>>> paths,
>>>>> also mentioned in https://sourceware.org/ml/cygwin/2013-08/msg00090.html
>>>>> (last item). I vaguely remember seeing a reason for this limitation in some
>>>>> mail but can't find it again. I think it would be good to remove this
>>>>> limitation because it breaks user expectations when working on
>>>>> case-sensitive drives.
>>>> The user expectation when using DOS paths is caseinsensitivity in the
>>>> first place.  But, as usual, there's no way to do this right, since
>>>> somebody will have another POV.  My stance is, don't use DOS paths when
>>>> using Cygwin.  At leats don't use DOS paths if you have any expectations
>>>> about special POSIX path handling on Cygwin.
>>> I use an application that uses Windows or mixed paths, I cannot influence
>>> it. So while I understand your POV, it would still be helpful to have path
>>> interpretation fully-featured. (If you point me to a place in winsup, I
>>> might even try to do something myself.)
>> I'm not going to apply a patch to do that.  DOS paths get no special
>> treatment, they are always handled with DOS/Windows defaults.
> Any last chance to get a distinction here between X:\dos\paths and 
> X:/mixed/paths?

No. It is the same path.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 24.10.2014, <1:49>

Sorry for my terrible english...


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