X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=iSK4MXYZeVRcfdwl Sm/4RirQn0ZTYHVTbQGnU5Y5JrTRyKVH8WD70EfcC0ANBCzgeb1OZvshL3ShgYEC clRvUw8+LVbJAB8cW3nIeR+w15Fc1Psgc1sfpn4FxAf26oj11I9BZ3x284L+5JYn ZuHIlyZhqS1zht5vGnhh3w975OQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=+iI9u+2MYkMBOqOoEoQSIP QYsQc=; b=qxuEqBszFJB/zSvFVyqe4uSwNY45EdS4bfgrlxbW9P0PmisYP8q2ft QyCK/GXrzRrnMPzEK1zqlYFwEzXiZzQAxUbTWKi1+fBnq4FXRAcoBOSRmjX0qcZG S0kkPSxNKBpQ0zJGTUwdA8MC18XcAZTZSwwXJdmhPKH9vRuc7MEa0= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=UD:msdn.microsoft.com, blogsmsdnmicrosoftcom, sk:blogsm, blogs.msdn.microsoft.com X-HELO: smtp-out-no.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: Strange git issue with a particular repo To: cygwin AT cygwin DOT com References: <201808050712 DOT w757Cx0a015412 AT freefriends DOT org> <4a856a8c-5a36-6758-5134-f102c03b0f4e AT mail DOT com> <201808050821 DOT w758LToi022033 AT freefriends DOT org> <8094cd2f-6f9b-4a13-6c31-2f556ea92513 AT cornell DOT edu> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <5c2fb7d1-9da6-9a61-cf5c-225b6fb5880d@SystematicSw.ab.ca> Date: Sun, 5 Aug 2018 09:21:05 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <8094cd2f-6f9b-4a13-6c31-2f556ea92513@cornell.edu> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes On 2018-08-05 08:01, Ken Brown wrote: > On 8/5/2018 5:31 AM, James Darnley wrote: >> You can clone it successfully on Windows if you enable case sensitivity, >> which is probably not recommended but possible with a registry change. > I wouldn't say this is not recommended.  It's documented in the Cygwin User's > Guide: > https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive > I've been setting up my Cygwin systems to be case sensitive for years with no > problems. Cygwin could now support doing so in its own directories on current Win releases: https://blogs.msdn.microsoft.com/commandline/2018/02/28/per-directory-case-sensitivity-and-wsl/ with currently documented interfaces: fsutil file {query|set}CaseSensitiveInfo [enable|disable] although this "flag" does not appear to be an inheritable attribute, so has to be manually applied recursively to subdirs. It also appears to be supported by DrvFS mount option case=off|dir|force, where the first two alternatives honour the flag, the second and third adds it to directories created on those mounts, and the third ignores the flag treating all names as case sensitive. This might be useful as a Windows git option, but not under Cygwin just now, unless someone added support for an option supporting it on earlier releases also. -- 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