I found the answer to the "when and why" question via ChatGPT, after multiple web searches failed to turn up anything useful, and even after discovering the spe

I found the answer to the "when and why" question via ChatGPT, after multiple web searches failed to turn up anything useful, and even after discovering the specific release that included the change (2.46, by the way), learning that the top result in Google for "git 2.46 release notes" leads to a 404 in Git's own Github repository. Nice. For anyone else interested in the "when and why", this StackOverflow answer [1] to a tangentially-related newb question summarizes and links to some of the specific commits, and this GitHub blog post [2] announcing what's new in that release, does describe the change in amongst a bunch of other stuff. Still, I would hope that for the sake of the millions of users out there who don't welcome the cognitive dissonance, confusion and breaking-out-of-flow that this kind of (lack of) communication produces, maintainers of such popular tools may think a little bit when updating their docs with such a significant change and perhaps call out the change front-and-centre. [1] https://stackoverflow.com/a/78727574/1134217 https://stackoverflow.com/a/78727574/1134217 [2] https://github.blog/open-source/git/highlights-from-git-2-46/ https://github.blog/open-source/git/highlights-from-git-2-46...