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

Re: [PATCH 1/2] init-db.c: honor case on case preserving fs

From
Torsten Bögershausen <tboegi@web.de>
Date
Feb 1, 2014, 12:17 UTC
Message-ID
<52ECE5EB.6090304@web.de>
In-Reply-To
<1391246067-30499-1-git-send-email-reubenhwk@gmail.com>
On 2014-02-01 10.14, Reuben Hawkins wrote:
Show 6 quoted lines
> Most case-insensitive filesystems are case-preserving. In these
> filesystems (such as HFS+ on OS X) you can name a file Filename.txt,
> then rename the file to FileName.txt.  That file will be accessible
> by both filenames, but the case is otherwise honored.  We don't want
> to have git ignore case on these case-preserving filesystem
> implementations.

Yes, we want. Because the file system will treat "Filename.txt" and "FileName.txt" the same. Whatever is on disc, the OS will not distinguish them. (On a case-insensitive HFS+ partition).

And when core.ignorecase == true, Git does the same what the OS does, ignore the case.

Could you describe the problems more in detail ?

Could you supply a test case, (or a short script) which shows the problem and makes it reproducable for others?

Which problems does your patch solve, which can not be solved
by setting core.ignorecase==false manually?
 
/Torsten
Previous: Reuben HawkinsNext: Junio C Hamano
Message 3 of 6 in “init-db.c: honor case on case preserving fs”
  1. 1/2 init-db.c: honor case on case preserving fsReuben Hawkins, Feb 1, 2014
  2. 2/2 init-db.c: factor out probe_case_sensitivity funcReuben Hawkins, Feb 1, 2014
  3. Torsten BögershausenFeb 1, 2014
  4. Junio C HamanoFeb 2, 2014
  5. Dmitry PotapovFeb 1, 2014
  6. Dmitry PotapovFeb 2, 2014

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.