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

Re: Q: description of file name encoding approach used by git

From
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 11, 2009, 16:08 UTC
Message-ID
<76718490902110808g47b3ce0bm24419c89b5cb4aaa@mail.gmail.com>
In-Reply-To
<85647ef50902110356l19870259t9de22fd8827ac144@mail.gmail.com>

On Wed, Feb 11, 2009 at 6:56 AM, Constantine Plotnikov <constantine.plotnikov@gmail.com> wrote:

> 3. As I understand, there is an unresolved problem with Mac OSX HFS+
> case insensitive file system due to file name normalization.

HFS+ can be configured to be case-sensitive, though it is not by default. However, this is only a problem if the repo contains > 1 filenames that collide in a case-insensitive filesystem, since HFS+ is case-preserving.

The larger HFS+ problem is that it performs Unicode NFD normalization, which is unfortunately lossy. There are some good links about the topic here: https://bugs.launchpad.net/bzr/+bug/172383

j.
Previous: Constantine Plotnikov
Message 2 of 2 in “Q: description of file name encoding approach used by git”
  1. Constantine PlotnikovFeb 11, 2009
  2. Jay SoffianFeb 11, 2009

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.