Git 2.47 Released With Improvements & Encouraging More Positive Code Reviews
([Programming] 5 Hours Ago
Git 2.47)
- Reference: 0001496664
- News link: https://www.phoronix.com/news/Git-2.47-Released
- Source link:
Git 2.47 is out today as the newest feature release to this immensely popular distributed revision control system.
Git 2.47 introduces a new experimental feature for incremental multi-pack indexes. This change is still experimental and the multi-pack reachability bitmaps feature will further extend the capabilities in the future.
Git 2.47 also introduces "for-each-ref" to more quickly find base branches. Git 2.47 also brings improved support for its "reftable" reference backend, better unit testing, and the Git mergetool command has a new tool configuration for Visual Studio Code.
When going through the [1]Git 2.47 release announcement I was also curious about the change:
* The reviewing guidelines document now explicitly encourages people to give positive reviews and how.
The documentation [2]patch is to the code re viewing guidelines to encourage more positive reviews:
"I saw some contributors hesitate to give a positive review on patches by their coworkers. When written well, a positive review does not have to be a hollow "looks good" that rubber stamps an useless approval on a topic that is not interesting to others.
Let's add a few paragraphs to encourage positive reviews, which is a bit harder to give than a review to point out things to improve."
See [3]this patch for the new recommendations for providing more positive code reviews.
Further insight into the prominent Git 2.47 changes can be found on the [4]GitHub blog .
[1] https://lore.kernel.org/lkml/xmqqa5fg9bsz.fsf@gitster.g/T/#u
[2] https://github.com/git/git/commit/92e24c8b79f94308936389387af7acb883773020
[3] https://github.com/git/git/commit/92e24c8b79f94308936389387af7acb883773020
[4] https://github.blog/open-source/git/highlights-from-git-2-47/
Git 2.47 introduces a new experimental feature for incremental multi-pack indexes. This change is still experimental and the multi-pack reachability bitmaps feature will further extend the capabilities in the future.
Git 2.47 also introduces "for-each-ref" to more quickly find base branches. Git 2.47 also brings improved support for its "reftable" reference backend, better unit testing, and the Git mergetool command has a new tool configuration for Visual Studio Code.
When going through the [1]Git 2.47 release announcement I was also curious about the change:
* The reviewing guidelines document now explicitly encourages people to give positive reviews and how.
The documentation [2]patch is to the code re viewing guidelines to encourage more positive reviews:
"I saw some contributors hesitate to give a positive review on patches by their coworkers. When written well, a positive review does not have to be a hollow "looks good" that rubber stamps an useless approval on a topic that is not interesting to others.
Let's add a few paragraphs to encourage positive reviews, which is a bit harder to give than a review to point out things to improve."
See [3]this patch for the new recommendations for providing more positive code reviews.
Further insight into the prominent Git 2.47 changes can be found on the [4]GitHub blog .
[1] https://lore.kernel.org/lkml/xmqqa5fg9bsz.fsf@gitster.g/T/#u
[2] https://github.com/git/git/commit/92e24c8b79f94308936389387af7acb883773020
[3] https://github.com/git/git/commit/92e24c8b79f94308936389387af7acb883773020
[4] https://github.blog/open-source/git/highlights-from-git-2-47/
fitzie