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

Git filesystem case-insensitive to case-sensitive system broken

From
SRSteven Robertson <srtrumpetaggie@gmail.com>
Date
Jan 6, 2017, 21:56 UTC
Message-ID
<CALwf_moJFqCKcc5Q=CC6aSSUAGqXEFDKrJUkdwov8shqBRK=yg@mail.gmail.com>
Hello,

I was doing development on a linux box on AWS, when we found a code bug that had me switching to running the code on a Mac instead. We discovered that we had accidentally named two files the same when looked at case-insensitively, which made git commands afterwards display the wrong thing. It looked like this (ignoring some things that aren't relevant):

$ git status
   modified:   tests/test_system/show_19_L.txt
no changes added to commit (use "git add" and/or "git commit -a")
$ git checkout tests/test_system/show_19_L.txt
$ git status
   modified:   tests/test_system/show_19_l.txt
no changes added to commit (use "git add" and/or "git commit -a")
$ git checkout tests/test_system/show_19_l.txt
$ git status
   modified:   tests/test_system/show_19_L.txt
no changes added to commit (use "git add" and/or "git commit -a")
$ diff tests/test_system/show_19_L.txt tests/test_system/show_19_l.txt
$

Those two files are different in our repo, and as such git thinks that we modified one of them when we try and pull it down from github again.

Thanks for looking at this! -- Steven

Next: Torsten Bögershausen
Message 1 of 2 in “Git filesystem case-insensitive to case-sensitive system broken”
  1. Steven RobertsonJan 6, 2017
  2. Torsten BögershausenJan 7, 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.