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:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=kBAS6sCkrPRPH7Ne
	P3MA8jFhYK37n6s60eJHuMdDSgpruMRlIbDbYelFvuc72RvP9usxWOP4SLLeZ61h
	3pQAVj/V6FGYoFg57VND8nBkR99tEVNTVyTXXDEKB5CTewYDTb6x9fdnTYzDw9+C
	e/wP2JiRe/BL0wwzL2EKAi99Hn0=
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:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=vkk+9+6RQIYmzjbqa+8i9J
	ITusA=; b=Y1IhWxUWQbBiC6TM/ZXeFKuiIeclginQ9BeN9SHV7gKhzUXH1pdKGc
	vBpRmCyH5h6fGTpAZ3P7VDiWcnI+M6TOu/RgM+8ROv0f1URM8V6PJRh4QWRgFDte
	Pr0Srd52o0aSWd3bN1muL/3tOXS4zQRef8rF54d02TuSWaaM15g+E=
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=0.1 required=5.0 tests=AWL,BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:split, arnoldskeevecom, sk:arnold, Cloning
X-HELO:	mout.gmx.com
Subject:	Re: Strange git issue with a particular repo
To:	cygwin AT cygwin DOT com
References:	<201808050712 DOT w757Cx0a015412 AT freefriends DOT org>
From:	john doe <johndoe65534 AT mail DOT com>
Cc:	arnold AT skeeve DOT com
Message-ID:	<4a856a8c-5a36-6758-5134-f102c03b0f4e@mail.com>
Date:	Sun, 5 Aug 2018 10:07:09 +0200
MIME-Version:	1.0
In-Reply-To:	<201808050712.w757Cx0a015412@freefriends.org>
X-IsSubscribed:	yes

On 8/5/2018 9:12 AM, arnold AT skeeve DOT com wrote:
> Hi All.
> 
> Please cc me on responses, as I don't subscribe to the list.
> 
> I'm using a 64 bit install on Windows 10. I just now did an update
> and it did not help.  The problem is with a particular repo only.
> (Or at least, I only see it with this particular repo.) On Linux, do:
> 
> 	git clone git://github.com/arnoldrobbins/bwk-awk
> 	cd bwk-awk
> 	git status
> 
> You should see something like this:
> 
> 	$ git clone git://github.com/arnoldrobbins/bwk-awk
> 	Initialized empty Git repository in /u/arnold/bwk-awk/.git/
> 	remote: Counting objects: 463, done.
> 	remote: Compressing objects: 100% (16/16), done.
> 	remote: Total 463 (delta 1), reused 6 (delta 1), pack-reused 444
> 	Receiving objects: 100% (463/463), 5.06 MiB | 1.77 MiB/s, done.
> 	Resolving deltas: 100% (79/79), done.
> 	$ cd bwk-awk
> 	$ git status
> 	# On branch master
> 	nothing to commit (working directory clean)
> 
> On Cygwin, something strange happens instead:
> 
> 	$ git clone git://github.com/arnoldrobbins/bwk-awk
> 	Cloning into 'bwk-awk'...
> 	remote: Counting objects: 463, done.
> 	remote: Compressing objects: 100% (16/16), done.
> 	remote: Total 463 (delta 1), reused 6 (delta 1), pack-reused 444
> 	Receiving objects: 100% (463/463), 5.06 MiB | 2.33 MiB/s, done.
> 	Resolving deltas: 100% (79/79), done.
> 	$ cd bwk-awk
> 	$ git status
> 	On branch master
> 	Your branch is up to date with 'origin/master'.
> 
> 	Changes not staged for commit:
> 	  (use "git add <file>..." to update what will be committed)
> 	  (use "git checkout -- <file>..." to discard changes in working directory)
> 
> 		modified:   regdir/Compare.T
> 		modified:   regdir/T.delete
> 		modified:   regdir/T.getline
> 		modified:   regdir/T.redir
> 		modified:   regdir/T.split
> 		modified:   regdir/T.sub
> 
> 	no changes added to commit (use "git add" and/or "git commit -a")
> 
> The "modified" files are from an earlier commit. Doing git reset --hard has
> no effect.
> 
> On cygwin:
> 
> 	$ git --version
> 	git version 2.17.0
> 
> On Linux:
> 
> 	$ git --version
> 	git version 1.7.1
> 
> But it also works OK on a Linux system with git 2.17.1.
> 
> Any help would be appreciated. I hope that you can reproduce it.
> 

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.

-- 
John Doe

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

- Raw text -