git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: bug: HEAD vs. head on case-insensitive filesystems

From
KHKenneth Hsu <kennethhsu@gmail.com>
Date
Jul 12, 2017, 02:37 UTC
Message-ID
<20170712023655.GA15598@lenny.localdomain>
In-Reply-To
<20170711071234.bj3kzfn5xii4e33w@sigill.intra.peff.net>
Show 9 quoted lines
> I was going to point you to the recent thread in
> 
>   http://public-inbox.org/git/87ziclb2pa.fsf@gmail.com/
> 
> 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".

Thanks, that makes sense. Perhaps it's best to just view my original message as, "here's a new example of where 'head' doesn't work".

Previous: Jeff King
Message 3 of 3 in “bug: HEAD vs. head on case-insensitive filesystems”
  1. Kenneth HsuJul 11, 2017
  2. Jeff KingJul 11, 2017
  3. Kenneth HsuJul 12, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.