tags:

views:

56

answers:

1
+6  Q: 

Git file rename

I wanted to rename a folder from "Frameworks" to "frameworks", but git would not let me add the new lowercase name.
I guess it treats filenames case insensitive, does it?

A git add frameworks/ -f didn't help

+6  A: 

You can try:

  • "git mv -f foo.txt Foo.txt"
  • to set ignorecase to false in the config file.

But the issue of case (on Windows for instance) is described in the msysgit issue 228

there is always an option to set ignorecase to false in the config file that will force Unix like Git semantics on top of NTFS.
Git supports this behavior but it is not the default - from NTFS point of view a.txt and A.txt are the same thing - so Git tries to preserve that as most users would expect

As a better workaround, you can

git mv foo.txt foo.txt.tmp && git mv foo.txt.tmp Foo.txt

, which also changes the case of the file as stored on disk.

This blog post illustrates the same issue on MacOs during a rebase:

The default on Mac OS X file systems is that they are case-insensitive. FFFFFF.gif is the same as ffffff.gif.
If you delete the file in question, just from the file system, not from the Git index, mind you, you can merge the branch in question, and have it restore the file as if nothing happened.
The steps are pretty simple:

$ rm file/in/question.gif
$ git merge trunk

Anyhow, remember what git mv stands for:

mv oldname newname
git add newname
git rm oldname

, so if newname and oldname clash, you need to make them different (even if it is only for a short period of time), hence the git mv foo.txt foo.txt.tmp && git mv foo.txt.tmp Foo.txt

VonC
I already tried `git mv` but it gave me `fatal: renaming 'Frameworks' failed: Invalid argument`
Erik Aigner
@Erik: what was the exact command line you tried?
VonC
Ok the 2 step `git mv` did work!
Erik Aigner