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

Problems with file name case on Windows.

From
martinvz <martin.von.zweigbergk@gmail.com>
Date
Apr 22, 2010, 20:54 UTC
Message-ID
<1271969657620-4947131.post@n2.nabble.com>

Under Cygwin, if you add a file "a" in one commit, then rename the file to "A" and commit again, both files will be in the new commit. Running the following line under Cygwin produces a commit with both files ("a" and "A"). Running it on Linux produces a commit with one file ("A"), as expected.

git init; git config core.ignorecase false; touch a; git add a; git commit -m a; mv a A; git add -A; git commit -m A

The problem seems to be with the "git add -A" part, since it is possible to get around the problem by running "git add A" followed by "git rm a" (or by using lower-level commands, I suppose). What are the chances of getting this fixed? It's mostly annoying when importing existing code where it's harder to use the add-rm workaround, since you don't know which files have changed file name case.

-- 
View this message in context: http://git.661346.n2.nabble.com/Problems-with-file-name-case-on-Windows-tp4947131p4947131.html
Sent from the git mailing list archive at Nabble.com.
Next: Tay Ray Chuan
Message 1 of 4 in “Problems with file name case on Windows.”
  1. martinvzApr 22, 2010
  2. Tay Ray ChuanApr 23, 2010
  3. Johannes SixtApr 23, 2010
  4. martinvzApr 23, 2010

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.