Git Rev News Edition 112 (June 30th, 2024)
Welcome to the 112th edition of Git Rev News, a digest of all things Git. For our goals, the archives, the way we work, and how to contribute or to subscribe, see the Git Rev News page on git.github.io.
Patrick Steinhardt sent an RFC patch to the mailing list that created a new “UpcomingBreakingChanges.md” document. The goal of the document was to inform users and developers of deprecations and breaking changes, and to encourage discussion of the direction of the project regarding these topics in advance.
Patrick noted that the changes listed in the document, along with links to mailing list threads where they had been discussed, were a work in progress with controversial and missing items, and that he didn’t want to push for a Git 3.0 release with the listed changes soon.
The idea for that new document had been discussed previously in a thread about a patch series from Patrick that introduced subcommands like get, set, etc, in git config. In that thread, after Patrick asked if we wanted to introduce a document to keep track of upcoming removals for a potential Git 3.0 release, Junio Hamano, the Git maintainer, replied to Patrick that in a few of his “What’s cooking” emails before the Git 2.44.0 release, he had written:
