Reputation: 102240
I was testing on my local machine (OS-X 10.10) which uses a case insensitive file system (HFS+ [CI]) - when I reset to the head:
$ git reset head --hard
$ git reset HEAD --hard
and
$ git checkout 4f2c
$ git checkout 4F2C
Have the exact same results. To my understanding GIT stores refs inside ./git/refs
but does the case sensitivity of the underlying file system affect the results?
Would I get the same results on a case sensitive file system?
Upvotes: 7
Views: 1118
Reputation: 78743
No, you would not get the same results on a case sensitive filesystem. If you ran:
git reset branch --head
on a case sensitive filesystem then that is not the same as running:
git reset BRANCH --hard
Since references are often stored on the filesystem (in the .git/refs/heads
folder), the case sensitivity of the filesystem comes into play. On a case sensitive filesystem, .git/refs/heads/branch
and .git/refs/heads/BRANCH
are two different files.
Note that even on a case insensitive filesystem, your references may end up "packed", in a file specifying on reference per line. In this case, your references are always case sensitive, regardless of your filesystem.
Upvotes: 5
Reputation: 201497
Yes, they are case insensitive. No, a case sensitive file system will not matter. Because git
refs are part of a SHA-1 hash, and those are hexadecimal digits (base-16, they just look like letters). At least for the commit-id. As pointed out by @EdwardThomson in the comments, a ref-name may (or may not) be case-sensitive (that depends on the underlying filesystem and whether or not the storage mechanism is loose or packed).
Upvotes: 5