[Bug] Unexpected behavior on case insensitive filesystems

Alex Brachet-Mialot· Jul 2, 2019, 17:22 UTC · lore

Branches behave weirdly for case insensitive filesystems, and I'm guessing other things as well. For example say I am on a branch other than master, checking out 'Master' will _work_, I will of course be on the right branch but git status will say I am on 'Master' (expected just 'master') and git branch will highlight no branch.

Bryan Turner· Jul 2, 2019, 19:05 UTC · re: Alex Brachet-Mialot · lore

Re: [Bug] Unexpected behavior on case insensitive filesystems

On Tue, Jul 2, 2019 at 10:23 AM Alex Brachet-Mialot <alexbrachetmialot@gmail.com> wrote:

Show 6 quoted lines

>
> Branches behave weirdly for case insensitive filesystems, and I'm
> guessing other things as well. For example say I am on a branch other
> than master, checking out 'Master' will _work_, I will of course be on
> the right branch but git status will say I am on 'Master' (expected
> just 'master') and git branch will highlight no branch.

This comes up on the list fairly often. A couple of recent threads are: https://public-inbox.org/git/d4d8d8208b6a41c380ecf20807763bcf@XCH15-05-02.nw.nos.boeing.com/t/#u https://public-inbox.org/git/CAGyf7-E3-0SiqweoX-uLotwcCcy5MSxG6Zh+DRo6zQPKqTQQpA@mail.gmail.com/t/#u

This also comes up for files within a repository: https://public-inbox.org/git/trinity-4a160867-2036-4f8a-8363-7bf2e021d840-1558184320864@3c-app-gmx-bs48/t/#u https://public-inbox.org/git/AANLkTi=87fUaOH3Y0PVeeH5N7oCVVJyKY3jsf93jw-t7@mail.gmail.com/t/#u

The replies to the first thread explain the behavior, why it does what it does, and why it hasn't been changed yet. It happens on case-insensitive macOS filesystems and on NTFS on Windows.

Hope this helps!

Bryan