Potential Same Name Bug

I hit an issue in Git today that seemed to be a bug. Basically what happened is in our master branch we had two files, one named something like "file_NAME.png" and another named "file_name.png" in the same folder. In the develop branch in the same repo we had removed the "file_NAME.png" file so that only the "file_name.png" file was left. If I clone the repo so I get master and then do "git checkout develop" I would see when running "git status" that I would have this message:

On branch develop
Your branch is up-to-date with 'origin/develop'.
Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

        deleted:    file_name.png

no changes added to commit (use "git add" and/or "git commit -a")

So when I move from master to develop that status would come up. If I ran "git reset --hard" I would no longer have that message. I also saw that when I do a git clone and specify to clone the develop branch that I would not see the git status above. Is this an issue where if one branch has two files of the same name where one gets removed that it will remove both instances of that file in another branch when you switch to it? I fixed this issue in our repo by removing the "file_NAME.png" file in the master branch, but it seems like this should be handled better in the case I described.