Detecting files that differ only in case being cloned onto a case-insensitive file system is a great feature. We recently ran into an issue when using the Nix build tool, which caches inputs based on a SHA hash, where it generated different hashes between Linux (w/ a case sensitive file system) and Mac (with a case insensitive one) machines.
Tracking that one down was pretty tricky. I didn't even consider that something at the Git level could be done to improve the situation!
The submitted story is an article. Some (including myself) find the prose and explanatory style more approachable than the release notes. Adding a link to the release notes is helpful. The "Because git != GitHub" is unnecessary.
Comments
Detecting files that differ only in case being cloned onto a case-insensitive file system is a great feature. We recently ran into an issue when using the Nix build tool, which caches inputs based on a SHA hash, where it generated different hashes between Linux (w/ a case sensitive file system) and Mac (with a case insensitive one) machines.
Tracking that one down was pretty tricky. I didn't even consider that something at the Git level could be done to improve the situation!
Because git != GitHub, the actual change log can be found here: https://public-inbox.org/git/xmqqtvgtkq46.fsf@gitster-ct.c.g...
The submitted story is an article. Some (including myself) find the prose and explanatory style more approachable than the release notes. Adding a link to the release notes is helpful. The "Because git != GitHub" is unnecessary.
That's an unofficial mirror of the release notes. Here's an official one: https://github.com/git/git/blob/master/Documentation/RelNote...