On Tue, Jul 04, 2017 at 10:19:09AM +0300, Konstantin Khomoutov wrote: > On Tue, Jul 04, 2017 at 12:00:49AM +0200, Ævar Arnfjörð Bjarmason wrote: > > > I don't have a OSX box, but was helping a co-worker over Jabber the > > other day, and he pasted something like: > > > > $ git merge-base github/master head > > > > Which didn't work for me, and I thought he had a local "head" branch > > until realizing that of course we were just resolving HEAD on the FS. > > > > Has this come up before? I think it makes sense to warn/error about > > these magic /HEAD/ revisions if they're not upper-case. > > > > This is likely unintentional and purely some emergent effect of how it's > > implemented, and leads to unportable git invocations. > > JFTR this is one common case of confusion on Windows as well. > To the point that I saw people purposedly using "head" on StackOverflow > questions. That is, they appear to think (for some reason) that > branches in Git have case-insensitive names and prefer to spell "head" > since it (supposedly) easier to type. The use of "head" also appears to be leading to some strange behavior when resolving refs on Windows. See the following issue in the git-for-windows project: https://github.com/git-for-windows/git/issues/1225 In summary, it seems that head and HEAD can resolve to different revisions when in a worktree.
