> On 23 Jan 2017, at 19:35, Junio C Hamano <[email protected]> wrote: > > Dakota Hawkins <[email protected]> writes: > >> 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. > > As I know I am on the To: line of the message I am responding to, > let me quicly let you know that I won't be responding to this thread > for a while as I don't recall what the discussion was about. I will > after I'll dig and find out what the thread was about but it won't > happen immediately. Sorry about that.
Problem: Git attributes for path names are generally case sensitive. However, on a case insensitive file system (e.g. macOS/Windows) they appear to be case insensitive (`*.bar` would match `foo.bar` and `foo.BAR`). That works great until a Git users joins the party with a case sensitive file system. For this Git user the attributes pattern only matches files with the exact case (*.bar` would match only `foo.bar`). Question/Proposal: Could we introduce some flag to signal that certain attribute patterns are always case insensitive? Thread: http://public-inbox.org/git/[email protected]/#t Cheers, Lars
