{"thread":{"id":"51417","subject":"[Bug] Unexpected behavior on case insensitive filesystems","startedAt":"2019-07-02T17:23:01Z","lastAt":"2019-07-02T19:06:09Z","messageCount":2,"participants":["Alex Brachet-Mialot","Bryan Turner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"378503","messageId":"CAOt2X9sqbpK2qaKk9uf7fL=WCdzJr4+bx-0CsgjssTKkEhd++Q@mail.gmail.com","threadId":"51417","inReplyTo":null,"subject":"[Bug] Unexpected behavior on case insensitive filesystems","fromName":"Alex Brachet-Mialot","fromEmail":"alexbrachetmialot@gmail.com","sentAt":"2019-07-02T17:22:48Z","receivedAt":"2019-07-02T17:23:01Z","isPatch":false,"sender":{"key":"alexbrachetmialot@gmail.com","avatar":null},"body":"Branches behave weirdly for case insensitive filesystems, and I'm\nguessing other things as well. For example say I am on a branch other\nthan master, checking out 'Master' will _work_, I will of course be on\nthe right branch but git status will say I am on 'Master' (expected\njust 'master') and git branch will highlight no branch.\n"},{"id":"378511","messageId":"CAGyf7-Ewm3A7h0vcbahMM+Jf=TcygVrkUob5YaAdH9HByh3asw@mail.gmail.com","threadId":"51417","inReplyTo":"CAOt2X9sqbpK2qaKk9uf7fL=WCdzJr4+bx-0CsgjssTKkEhd++Q@mail.gmail.com","subject":"Re: [Bug] Unexpected behavior on case insensitive filesystems","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2019-07-02T19:05:56Z","receivedAt":"2019-07-02T19:06:09Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"On Tue, Jul 2, 2019 at 10:23 AM Alex Brachet-Mialot\n<alexbrachetmialot@gmail.com> wrote:\n>\n> Branches behave weirdly for case insensitive filesystems, and I'm\n> guessing other things as well. For example say I am on a branch other\n> than master, checking out 'Master' will _work_, I will of course be on\n> the right branch but git status will say I am on 'Master' (expected\n> just 'master') and git branch will highlight no branch.\n\nThis comes up on the list fairly often. A couple of recent threads are:\nhttps://public-inbox.org/git/d4d8d8208b6a41c380ecf20807763bcf@XCH15-05-02.nw.nos.boeing.com/t/#u\nhttps://public-inbox.org/git/CAGyf7-E3-0SiqweoX-uLotwcCcy5MSxG6Zh+DRo6zQPKqTQQpA@mail.gmail.com/t/#u\n\nThis also comes up for files within a repository:\nhttps://public-inbox.org/git/trinity-4a160867-2036-4f8a-8363-7bf2e021d840-1558184320864@3c-app-gmx-bs48/t/#u\nhttps://public-inbox.org/git/AANLkTi=87fUaOH3Y0PVeeH5N7oCVVJyKY3jsf93jw-t7@mail.gmail.com/t/#u\n\nThe replies to the first thread explain the behavior, why it does what\nit does, and why it hasn't been changed yet. It happens on\ncase-insensitive macOS filesystems and on NTFS on Windows.\n\nHope this helps!\n\nBryan\n"}]}