{"thread":{"id":"48461","subject":"Git case-sensitivity bug","startedAt":"2018-05-10T19:46:53Z","lastAt":"2018-05-10T20:09:47Z","messageCount":2,"participants":["Cliff","Bryan Turner"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"347300","messageId":"CAKsGxtUpu66fj=puTxioTwCrint+U83a3R-DPhx5gXKF8Phm3A@mail.gmail.com","threadId":"48461","inReplyTo":null,"subject":"Git case-sensitivity bug","fromName":"Cliff","fromEmail":"miliways@gmail.com","sentAt":"2018-05-10T19:46:46Z","receivedAt":"2018-05-10T19:46:53Z","isPatch":false,"sender":{"key":"miliways@gmail.com","avatar":null},"body":"I believe I have discovered a bug with git tools.\n\nIf you create a git branch, you can refer to that branch with\ncase-insensitive alterations and it will track as the same branch.\n\nIf I create branch \"test\" I cannot then create branch \"Test\" because\nthe same name is already used.\n\nHowever, git commands ARE case-sensitive, causing unspecified behavior!\n\nIf you create branch \"test\" and then run \"git checkout Test\" and then\nrun \"git branch\" it will list the branches \"master\" and \"test\" and\nNEITHER ONE will be flagged * as the current branch! (It does not list\nTest and does not show any branch as being the current branch)\n\nAs far as git is concerned... you're not on a branch! But you're\nsecretly on the \"test\" branch.\n\nAlso, I think this may cause further issues. Switching to \"test\" tells\nme that I am 1 commit behind master, but switching to \"Test\" gives no\nsuch message, and appears to want me to --set-upstream again, for the\nsame branch.\n\nThis is really bad behavior.\n\nI'm on MacOS so this may be unique to the Mac version of git tools.\n"},{"id":"347308","messageId":"CAGyf7-E3-0SiqweoX-uLotwcCcy5MSxG6Zh+DRo6zQPKqTQQpA@mail.gmail.com","threadId":"48461","inReplyTo":"CAKsGxtUpu66fj=puTxioTwCrint+U83a3R-DPhx5gXKF8Phm3A@mail.gmail.com","subject":"Re: Git case-sensitivity bug","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2018-05-10T20:09:32Z","receivedAt":"2018-05-10T20:09:47Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"Hey Cliff,\n\nOn Thu, May 10, 2018 at 12:46 PM Cliff <miliways@gmail.com> wrote:\n\n> I believe I have discovered a bug with git tools.\n\n> If you create a git branch, you can refer to that branch with\n> case-insensitive alterations and it will track as the same branch.\n\nThis comes up on the list fairly often on the list. The most recent thread\nis here:\nhttps://public-inbox.org/git/d4d8d8208b6a41c380ecf20807763bcf@XCH15-05-02.nw.nos.boeing.com/\n\nThe replies to that thread explain the behavior, why it does what it does,\nand why it hasn't been changed yet. It happens on case-insensitive macOS\nfilesystems and on NTFS on Windows.\n\nHope this helps!\nBryan Turner\n"}]}