Apologies for the delayed bump. I think because we're talking about affecting the behavior of .gitattributes that it would be better to have a distinct .gitattributes option, whether or not you also have a similar config option. Since .gitattributes is versioned and config options are not, I think this takes it out of the realm of personal preference. It's already too easy for somebody to screw up and not have a "required" filter driver (e.g. git lfs) configured and damage a repo by getting unnoticed and unfiltered content committed. I would love a .gitconfig option I could set that would let me stop manually ignoring case in globs for git commands, but this might actually make things worse for people if it were included as a config option only -- suddenly attributes could be applied to different files for different people. Of course, if git supported a subset of config options you could actually version and ensure everybody else has, this wouldn't be a problem ;) So, I think the correct (for today) solution is to have two options. One for .gitattributes globs and one for everything else. I realize that this might be somewhat controversial, so I wanted to see what everybody thought.