Conversation

@eater

I'm not sure breaking W3C's standards and various RFCs (3986 as one example) is something I'd call a feature.

Besides that, it's ignoring the case-sensitivity handling git itself imposes, the very tool it builds upon. Keep calling it what you want, it leads to real-world problems and that's what I call a bug.