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:from:message-id:date:to:subject:cc:references
	:in-reply-to:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=uhpymJaJjlVFBcW2
	7RcxWvdvKR9SXD58IRr2YgnyhIt3XXumwG6Bk2M4HSF41iFlFnAeFMsPPDdmqkeB
	n6P54ealGZFEiqI+Ko6VEcrdVuIxbsgendqkf/pQAEA86ui9MsLLRSHoWcPqONjN
	zLsLTyqxUE4x7jVXgIORdfRXzZk=
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:from:message-id:date:to:subject:cc:references
	:in-reply-to:mime-version:content-type
	:content-transfer-encoding; s=default; bh=gDxcNonkgrSwam9kpn0U9q
	ECtbE=; b=Rg632RjMBUSpZi6uG6T7wFZ8gclPv1QLH6SGn7hLr0A3d+i4LhgVJE
	fn6VfgmuquUpEv/JMSUXeAmUn8MWNg3pNt2k0BA1J+kcs+DVQA8/aXPMsqYtR7aA
	eaTF9y4aITDrlU5xHdov4Qu7mD8A5dWwGEzthc1RRqkLJU/MgkpZU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=league
X-HELO: freefriends.org
X-Envelope-From: arnold AT skeeve DOT com
From: arnold AT skeeve DOT com
Message-Id: <201808050821.w758LToi022033@freefriends.org>
Date: Sun, 05 Aug 2018 02:21:29 -0600
To: johndoe65534 AT mail DOT com, cygwin AT cygwin DOT com
Subject: Re: Strange git issue with a particular repo
Cc: arnold AT skeeve DOT com
References: <201808050712 DOT w757Cx0a015412 AT freefriends DOT org> <4a856a8c-5a36-6758-5134-f102c03b0f4e AT mail DOT com>
In-Reply-To: <4a856a8c-5a36-6758-5134-f102c03b0f4e@mail.com>
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi.

john doe <johndoe65534 AT mail DOT com> wrote:

> Linux is case sensitive and Windows is case preserving.
> That is probably the issue here, did the case of the files has been 
> changed (rename 100%)?
>
> https://docs.microsoft.com/en-us/vsts/repos/git/case-sensitivity?view=vsts
>
> In other words, on "Cygwin" git can not handle files defering only by 
> the case.

It's possible, but I don't think so.  Is there a straightforward way to
tell?  Although I've been using git for a while, I'm not a major league
guru.

Thanks!

Arnold

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