-
a little less than 3 years after the release of git they began to address case insensitive filesystems github.com/git/git/commit/b560707a1da841d2430d5d1eaeca0f63ddf4aae7Permalink
♻️ 1 Retweets ❤️ 1 Favorite Mood -2 🙁
-
About a month after those failing tests were added, git got a configuration optionPermalink
core.ignorecasegithub.com/git/git/commit/0a9b88b7dee70bd36d35b7857640a18ee3adeef1 -
And about a month after that, auto-detection made it so most people didn't need to worry about the config github.com/git/git/commit/2455406ab1b0e2b0ad9e5273b9aef6c739d5b8fePermalink
-
But after all these years, it's still something unsuspecting devs run into (look at all those upvotes) stackoverflow.com/questions/17683458/how-do-i-commit-case-sensitive-only-filename-changes-in-gitPermalink
-
A few years ago, the docs got updated so people wouldn't think they're making things better, when it probably makes things worse github.com/git/git/commit/48294b512a7c307d57ed5a9f5dbe466aeba6dadePermalink
-
I love the release notes for that doc change > Clarify that setting core.ignoreCase to deviate from reality would not turn a case-incapable filesystem into a case-capable one. github.com/git/git/blob/142430338477d9d1bb25be66267225fb58498d92/Documentation/RelNotes/2.19.0.txt#L334Permalink
-
This bit of code archaeology brought to you by an app that crashed because an asset's filename got a capitalization change and didn't get pushed upstream. It took a fair bit of teamwork to get to the bottom of this particular "works on my machine" incident