* Bug: Git checkout case Insensitive branch name compare
@ 2017-07-10 20:15 kinchit raja
2017-07-11 7:38 ` Jeff King
0 siblings, 1 reply; 2+ messages in thread
From: kinchit raja @ 2017-07-10 20:15 UTC (permalink / raw)
To: git
Bugs Details:
Git checkout case Insensitive branch name compare
Steps to Reproduce:
I have a remote branch which is as shown below.
Example: feature_12345_write.netCodeForSomeFeature
I used the git command on git bash and typed
"feature_12345_write.NetCodeForSomeFeature" thinking I am mapping
"feature_12345_write.netCodeForSomeFeature" locally.
So after I got the branch locally, I tried git pull and I see the following
"Your configuration specifies to merge with the ref
'refs/heads/feature_12345_write.NetCodeForSomeFeature' from the
remote, but no such ref was fetched.
Although when I did "git log", it shows proper history for
"feature_12345_write.netCodeForSomeFeature" branch.
However when I use the command "git pull --rebase origin branch" it
says "fatal: Couldn't find remote ref
feature_12345_write.NetCodeForSomeFeature"
Because the remote branch has 'n' instead of 'N' in '.net' for branch name.
This is because I used "git checkout branch" instead of "git checkout
branch origin/remote branch name" since the local branch name I wanted
was the same as the remote branch name.
I don't see this in other branches.
I think the command is not considering case sensitivity of characters
in the branch name.
Thanks.
--
Best Regards,
Kinchit Raja
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bug: Git checkout case Insensitive branch name compare
2017-07-10 20:15 Bug: Git checkout case Insensitive branch name compare kinchit raja
@ 2017-07-11 7:38 ` Jeff King
0 siblings, 0 replies; 2+ messages in thread
From: Jeff King @ 2017-07-11 7:38 UTC (permalink / raw)
To: kinchit raja; +Cc: git
On Mon, Jul 10, 2017 at 01:15:40PM -0700, kinchit raja wrote:
> Bugs Details:
>
> Git checkout case Insensitive branch name compare
Right, this is known. Branch names (and all ref names) are case
sensitive in Git. Storage on a case-insensitive filesystem may lead to
confusion if you mix the cases. Sometimes it will work, and sometimes it
will create quite confusing results. One suggested path forward is to
encode characters in the filesystem. See:
http://public-inbox.org/git/20170705083611.jgxbp4sqogicfwdb@sigill.intra.peff.net/
and further down-thread:
http://public-inbox.org/git/xmqqo9sxdwjp.fsf@gitster.mtv.corp.google.com/
for some recent discussion.
-Peff
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-07-11 7:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-07-10 20:15 Bug: Git checkout case Insensitive branch name compare kinchit raja
2017-07-11 7:38 ` Jeff King
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).