mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <>
To: Kenneth Hsu <>
Subject: Re: bug: HEAD vs. head on case-insensitive filesystems
Date: Tue, 11 Jul 2017 03:12:34 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20170711033236.GA11492@lenny.localdomain>

On Mon, Jul 10, 2017 at 08:32:36PM -0700, Kenneth Hsu wrote:

> I'm not sure what the general consensus is regarding the use of "head"
> vs. "HEAD" on case insensitive filesystems, but it appears that some
> confusing behavior (bug?) may have arisen.

Generally, the advice on "head" is "don't". It's an accident that
it works at all, and as you noticed, there are odd corner cases. There
are similar oddities when mixing and matching case for other refnames on
case-insensitive filesystems, too.

I was going to point you to the recent thread in

but I see you already participated there. So if your mail here is
"here's a summary of how HEAD/head don't quite work", then OK, that
might be handy. But I think the ultimate resolution is not "let's make
them work", but "let's consistently enforce case-sensitivity in ref
names, regardless of the underlying filesystem".


  reply	other threads:[~2017-07-11  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11  3:32 bug: HEAD vs. head on case-insensitive filesystems Kenneth Hsu
2017-07-11  7:12 ` Jeff King [this message]
2017-07-12  2:37   ` Kenneth Hsu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

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).