|
|
|
|
|
by sirmarksalot
3103 days ago
|
|
I disagree here. Case-insensitive file systems have existed for decades, and are part of the development landscape. Any tool that works across multiple machines needs to support them. In this case, I blame Bitbucket, for not providing any way to treat this as a merge conflict. |
|
Edit: To add, how is git supposed to handle two files with the same name -- as is the case -- with a case insensitive file system? You can't have two files with the "same" name.
Is entirely different than In any other platform ls file1 FILE1 would show two different files, but on OSX, it'll show the same file twice.