Just curious, as like most people I'm far too busy to study the release notes of every version update of every tool I regularly use. However it seems like quite a significant UX (or DX?) change to deprecate "git config --list" in favour of "git config list". I'm sure there are reasons for this, the subcommand approach is probably easier for newbies to learn than the flag-style UX, and it certainly makes the docs easier to read <i>if you've never used git before and are learning it for the first time</i>.<p>However I just stumbled across this change by chance when searching for the syntax and found that the docs page [0] does absolutely nothing to highlight the fact that this has changed and so seems to contradict every other blog post and article in the entire WWW that tells you to use --list.<p>For a few minutes I thought I was going insane. Eventually, scrolling down a lot, I found the words "DEPRECATED MODES: The following modes have been deprecated in favor of subcommands. It is recommended to migrate to the new syntax."<p>Seriously, who thinks like this? Who has such contempt for their users that they would change the UX of a decades-old tool used by millions and not bother to put a warning at the top of the current doc page along the lines of "hey guys, we just made a major change here, so don't worry if all the other websites out there seem to contradict this, click here to read more about the change and the reasons behind it..." ?<p>[0] https://git-scm.com/docs/git-config
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.<p>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.<p>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.<p>[1] <a href="https://stackoverflow.com/a/78727574/1134217" rel="nofollow">https://stackoverflow.com/a/78727574/1134217</a><p>[2] <a href="https://github.blog/open-source/git/highlights-from-git-2-46/" rel="nofollow">https://github.blog/open-source/git/highlights-from-git-2-46...</a>