Bug 47999 - git version update
Summary: git version update
Alias: None
Product: Sisyphus
Classification: Development
Component: git (show other bugs)
Version: unstable
Hardware: all Linux
: P5 normal
Assignee: Dmitry V. Levin
QA Contact: qa-sisyphus
Depends on:
Blocks: 46625
  Show dependency tree
Reported: 2023-10-13 16:04 MSK by Arseny Maslennikov
Modified: 2023-11-06 00:50 MSK (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Arseny Maslennikov 2023-10-13 16:04:26 MSK
Пользователи git в целях, не связанных с сопровождением пакетов и сборочницей, хотели бы видеть в репозитории более актуальный git.

С моей личной колокольни особенно интересными выглядят следующие нововведения и исправления:
 * "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.
 * 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
 * "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.
 * 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.
Comment 1 Arseny Maslennikov 2023-10-13 23:06:52 MSK
Нашлась ещё более веская яркая причина обновиться с 2.33.*:
 * In addition to GnuPG, ssh public crypto can be used for object and
   push-cert signing.  Note that this feature cannot be used with
   ssh-keygen from OpenSSH 8.7, whose support for it is broken.  Avoid
   using it unless you update to OpenSSH 8.8.
Comment 2 Repository Robot 2023-11-06 00:50:58 MSK
git-2.42.1-alt1 -> sisyphus:

 Thu Nov 02 2023 Dmitry V. Levin <ldv@altlinux> 2.42.1-alt1
 - 2.42.0 -> 2.42.1 (closes: #47999).
 Mon Aug 21 2023 Dmitry V. Levin <ldv@altlinux> 2.42.0-alt1
 - 2.33.8 -> 2.42.0.