On Fri, Mar 21, 2008 at 7:07 PM, Frank <streamlake@xxxxxxxxxx> wrote: > Hi, > Don't know exactly if this is a bug or a feature or something in the > middle, but I have a lot of problems while changing just the casing of > file names and using git mv und cygwin. Here's a test case: > > mkdir testrename > cd testrename > git init > echo "AAA" >aaa.txt > echo "BBB" >bbb.txt > git add aaa.txt > git add bbb.txt > git commit -m "First commit" > git checkout -b new_branch > git mv aaa.txt ccc.txt > git commit -a -m "Moved file" > echo "NEW AAA" >Aaa.txt > git add Aaa.txt > git commit -m "Added Aaa" > #aaa.txt exists in master, Aaa.txt in new_branch > git checkout master I wonder do you really need to have two files on different branches whose name only differ by case, especially when you work on case insensitive filesystem? I suspect the answer is no. In this case, you can choose one policy for file naming and stick to it. For instance, that all names should be in low case except Makefile, or something like that. This policy can be enforced using pre-commit hook. Dmitry -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
