Re: Possible minor bug in Git

From: Philip Oakley <philipoakley@iee.org>
Date: Feb 9, 2019, 18:19 UTC
Message-ID: <788eefef-f677-f0ce-7e02-dd85b11da78a@iee.org>
In-Reply-To: <nycvar.QRO.7.76.6.1902072040360.41@tvgsbejvaqbjf.bet>

Hi Guiseppe,

On 07/02/2019 19:41, Johannes Schindelin wrote:

Show 5 quoted lines

> Hi Giuseppe,
>
> On Wed, 6 Feb 2019, Giuseppe Crinò wrote:
>
>> I wanted to have a look at the bug, and I can correctly reproduce it using version 2.20.1.windows.1.

Thank you for having a look.

The root cause of the issues will most probably be use of a case insensitive file system on Windows (and Mac). There is a configuration flag `core.ignoreCase` [1] that is normally auto detected that can be used to decide when the checks should be done and advice [2] or warnings given.

There are also similar case issues with branch names should you want to go that far. In any case you should probably at least cover the full utf-8 filenames, not just ascii ones.

Show 14 quoted lines

>>
>> To start to even think of fixing this bug I need to build the source for Windows, but I got lost on how to do that.
> Does this help?
>
> https://github.com/git-for-windows/git/wiki/Building-Git
>
> Ciao,
> Johannes
>
>> Is it correct that I should cross-compile from a POSIX system (GNU/Linux), using x86_64-w64-mingw32-gcc and Gnulib to produce a static executable?
>>
>> Am I missing something? How does people here build for Windows?
>>
>> Giuseppe

--

Philip

[1] https://git-scm.com/docs/git-config#git-config-coreignoreCase

[2] https://git-scm.com/docs/git-config#git-config-advice