On our Ubuntu server, I can create both foo.txt and Foo.txt in a folder. On my OSX machine, those are considered the same file.
Three reasons that's no big deal: 1) We never create both foo.txt and Foo.txt. Why would we? (OK, that's a bit snarky.) :) 2) We're developing on the system that's more restrictive (doesn't allow caps and non-caps versions) and pushing to the one that's more permissive. So nothing will get lost in the process. If we were going the other way, or migrating from Linux machines, I could see it being a problem. 3) If this is really a big deal to someone, they can configure OSX to use a case-sensitive file system. May cause other side effects (some Mac backup utilities may ignore either Foo.txt or foo.txt when backing up), but it can be done.
Three reasons that's no big deal: 1) We never create both foo.txt and Foo.txt. Why would we? (OK, that's a bit snarky.) :) 2) We're developing on the system that's more restrictive (doesn't allow caps and non-caps versions) and pushing to the one that's more permissive. So nothing will get lost in the process. If we were going the other way, or migrating from Linux machines, I could see it being a problem. 3) If this is really a big deal to someone, they can configure OSX to use a case-sensitive file system. May cause other side effects (some Mac backup utilities may ignore either Foo.txt or foo.txt when backing up), but it can be done.