{"thread":{"id":"46349","subject":"Bug: Git checkout case Insensitive branch name compare","startedAt":"2017-07-10T20:15:46Z","lastAt":"2017-07-11T07:38:42Z","messageCount":2,"participants":["kinchit raja","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"324104","messageId":"CAKvSMhhO7RwiZfpcLR3cK2TXF-v9MrO1N33t8BqX=8f9z=Gd0w@mail.gmail.com","threadId":"46349","inReplyTo":null,"subject":"Bug: Git checkout case Insensitive branch name compare","fromName":"kinchit raja","fromEmail":"kinchit15@gmail.com","sentAt":"2017-07-10T20:15:40Z","receivedAt":"2017-07-10T20:15:46Z","isPatch":false,"sender":{"key":"kinchit15@gmail.com","avatar":null},"body":"Bugs Details:\n\nGit checkout case Insensitive branch name compare\n\nSteps to Reproduce:\n\n I have a remote branch which is as shown below.\nExample: feature_12345_write.netCodeForSomeFeature\n\n I used the git command on git bash and typed\n\"feature_12345_write.NetCodeForSomeFeature\" thinking I am mapping\n\"feature_12345_write.netCodeForSomeFeature\" locally.\n\nSo after I got the branch locally, I tried git pull and I see the following\n\"Your configuration specifies to merge with the ref\n'refs/heads/feature_12345_write.NetCodeForSomeFeature' from the\nremote, but no such ref was fetched.\n\n Although when I did \"git log\", it shows proper history for\n\"feature_12345_write.netCodeForSomeFeature\" branch.\n\nHowever when I use the command \"git pull --rebase origin branch\" it\nsays \"fatal: Couldn't find remote ref\nfeature_12345_write.NetCodeForSomeFeature\"\nBecause the remote branch has 'n' instead of 'N' in '.net' for branch name.\n\nThis is because I used \"git checkout branch\" instead of \"git checkout\nbranch origin/remote branch name\" since the local branch name I wanted\nwas the same as the remote branch name.\n\nI don't see this in other branches.\n\nI think the command is not considering case sensitivity of characters\nin the branch name.\n\nThanks.\n\n-- \nBest Regards,\nKinchit Raja\n"},{"id":"324161","messageId":"20170711073836.3nclljuzqgwdg6t5@sigill.intra.peff.net","threadId":"46349","inReplyTo":"CAKvSMhhO7RwiZfpcLR3cK2TXF-v9MrO1N33t8BqX=8f9z=Gd0w@mail.gmail.com","subject":"Re: Bug: Git checkout case Insensitive branch name compare","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-07-11T07:38:36Z","receivedAt":"2017-07-11T07:38:42Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Jul 10, 2017 at 01:15:40PM -0700, kinchit raja wrote:\n\n> Bugs Details:\n> \n> Git checkout case Insensitive branch name compare\n\nRight, this is known. Branch names (and all ref names) are case\nsensitive in Git. Storage on a case-insensitive filesystem may lead to\nconfusion if you mix the cases. Sometimes it will work, and sometimes it\nwill create quite confusing results. One suggested path forward is to\nencode characters in the filesystem. See:\n\n  http://public-inbox.org/git/20170705083611.jgxbp4sqogicfwdb@sigill.intra.peff.net/\n\nand further down-thread:\n\n  http://public-inbox.org/git/xmqqo9sxdwjp.fsf@gitster.mtv.corp.google.com/\n\nfor some recent discussion.\n\n-Peff\n"}]}