title: How to prevent git from committing two files with names differing only in case?
body: <p>We develop in a mixed environment - some people work on Macs and some work on Linux. This has proven to be a bit of a challenge at times, as those people who work on Linux are used to having their filesystems be case sensitive, so there's no issue committing (accidentally or otherwise) multiple files differing just by case. (e.g. <code>FileName.ext</code> versus <code>filename.ext</code>)</p>
  
  <p>However, when the people on Macs go to check out the repository, having a case-insensitive filesystem means that the two files - differing only in case - overwrite each other and cause general havoc.</p>
  
  <p>I know that there are various git settings to help people on case-insensitive filesystems work better with case changes (e.g. <code>core.ignorecase</code>), but these don't solve the issue where there's two different files in the repository, only differing by case.</p>
  
  <p>I realize that the only way to fix it is to make sure the Linux people don't commit the two files differing only in case in the first place. -- Is there some setting in git which will pop up a warning or error if a user on a case-sensitive filesystem attempts to commit file(s) which would be confused with each other on a case-insensitive filesystem?</p>