1 Git 2.25.2 Release Notes
2 ========================
7 * Minor bugfixes to "git add -i" that has recently been rewritten in C.
9 * An earlier update to show the location of working tree in the error
10 message did not consider the possibility that a git command may be
11 run in a bare repository, which has been corrected.
13 * The "--recurse-submodules" option of various subcommands did not
14 work well when run in an alternate worktree, which has been
17 * Running "git rm" on a submodule failed unnecessarily when
18 .gitmodules is only cache-dirty, which has been corrected.
20 * "git rebase -i" identifies existing commits in its todo file with
21 their abbreviated object name, which could become ambigous as it
22 goes to create new commits, and has a mechanism to avoid ambiguity
23 in the main part of its execution. A few other cases however were
24 not covered by the protection against ambiguity, which has been
27 * The index-pack code now diagnoses a bad input packstream that
28 records the same object twice when it is used as delta base; the
29 code used to declare a software bug when encountering such an
30 input, but it is an input error.
32 * The code to automatically shrink the fan-out in the notes tree had
33 an off-by-one bug, which has been killed.
35 * "git check-ignore" did not work when the given path is explicitly
36 marked as not ignored with a negative entry in the .gitignore file.
38 * The merge-recursive machinery failed to refresh the cache entry for
39 a merge result in a couple of places, resulting in an unnecessary
40 merge failure, which has been fixed.
42 * Fix for a bug revealed by a recent change to make the protocol v2
45 * "git merge signed-tag" while lacking the public key started to say
46 "No signature", which was utterly wrong. This regression has been
49 * MinGW's poll() emulation has been improved.
51 * "git show" and others gave an object name in raw format in its
52 error output, which has been corrected to give it in hex.
54 * Both "git ls-remote -h" and "git grep -h" give short usage help,
55 like any other Git subcommand, but it is not unreasonable to expect
56 that the former would behave the same as "git ls-remote --head"
57 (there is no other sensible behaviour for the latter). The
58 documentation has been updated in an attempt to clarify this.
60 Also contains various documentation updates, code clean-ups and minor fixups.
projects / thirdparty / git.git / blob