Bug 47999

Пользователи git в целях, не связанных с сопровождением пакетов и сборочницей, хотели бы видеть в репозитории более актуальный git.

С моей личной колокольни особенно интересными выглядят следующие нововведения и исправления:
https://github.com/git/git/blob/master/Documentation/RelNotes/2.38.0.txt:
 * "git rebase -i" learns to update branches whose tip appear in the
   rebased range with "--update-refs" option.
 * When "git merge" finds that it cannot perform a merge, it should
   restore the working tree to the state before the command was
   initiated, but in some corner cases it didn't.
https://github.com/git/git/blob/master/Documentation/RelNotes/2.39.0.txt:
 * The way "git repack" created temporary files when it received a
   signal was prone to deadlocking, which has been corrected.
 * `git rebase --update-refs` would delete references when all
   `update-ref` commands in the sequencer were removed, which has been
   corrected.
https://github.com/git/git/blob/master/Documentation/RelNotes/2.41.0.txt:
 * "git format-patch" honors the src/dst prefixes set to nonstandard
   values with configuration variables like "diff.noprefix", causing
   receiving end of the patch that expects the standard -p1 format to
   break.  "format-patch" has been taught to ignore end-user configuration
   and always use the standard prefixes.

   This is a backward compatibility breaking change.
 * "git blame --contents=<file> <rev> -- <path>" used to be forbidden,
   but now it finds the origins of lines starting at <file> contents
   through the history that leads to <rev>.
 * The output given by "git blame" that attributes a line to contents
   taken from the file specified by the "--contents" option shows it
   differently from a line attributed to the working tree file.
 * "git send-email" learned to give the e-mail headers to the validate
   hook by passing an extra argument from the command line.
 * "git send-email" learned "--header-cmd=<cmd>" that can inject
   arbitrary e-mail header lines to the outgoing messages.
https://github.com/git/git/blob/master/Documentation/RelNotes/2.42.0.txt:
 * During a cherry-pick or revert session that works on multiple
   commits, "git status" did not give correct information, which has
   been corrected.
   (merge a096a889f4 jk/cherry-pick-revert-status later to maint).

Исправления, может быть, к нам и так попадают, но дело не только в них. Соответственно, я бы хотел увидеть хотя бы 2.41.