Browse Source
-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE4fA2sf7nIh/HeOzvsLXohpav5ssFAl5xSg0ACgkQsLXohpav 5suNcw//cAfPWi2SU7zYNfylcBew7r21WQpqRvip+0s5vc5Pgj8tZEsFTDCl4ARR 0W7yaAoR4te/imLkGnij6tvEmuJMb+McQJYKQA5EqrkigloEy36dCYrDbA/saRa1 SSXp6P4zwl4iAPYa31AIZImhnI1a3pIzv3aYKEA3ecCG++vPxeW5a7frqIggvMJG g1SvCsjEqU6agRCePKjBZ6rbl7OJMnZGt+mfW1ymfCu+37NC5ubC3vSsAcy4SqVA KVmwe63NygnxczGvda/J4q2FO/Qb4OyvItdtrHMGwoy1MkldFCebmfkd+HBHHo5f Pg5lWcgf91YtEw98DSHRlFbXwMokxac8fiIX+X4m742Nu61BVgHff+EOJNeVuiV3 xe1ks51BQP6S6IZBXNg0CndmfVls8lbnWomfuYpLPraLRAGHm7eoTJz6/J0FnbVt LkDvKG7kyYcqswAlMKcSjQkxdzYg9lJPxM7KOaNF6XmKDnV4KJNBeu+1q456c9OF e10tiqQRyXwPPXxJtLcCCiAtb1oua7D9OPmBSYxXvoTeOqq3HtVuOVdQGJXpYvqV oGjx738AvFPXnsSybca+gkxAWzC6fDbyIJfqFO3dIIgsHqbyYQPRlrUG+4vPG9wc UZdK3XMNQ3K+EPABV0LhbgC0B7dU2n5NmKLNWF4TsZ/If5cySiU= =RZCX -----END PGP SIGNATURE----- Sync with Git 2.25.2 Signed-off-by: Junio C Hamano <gitster@pobox.com>maint
Junio C Hamano
5 years ago
3 changed files with 88 additions and 40 deletions
@ -0,0 +1,60 @@
@@ -0,0 +1,60 @@
|
||||
Git 2.25.2 Release Notes |
||||
======================== |
||||
|
||||
Fixes since v2.25.1 |
||||
------------------- |
||||
|
||||
* Minor bugfixes to "git add -i" that has recently been rewritten in C. |
||||
|
||||
* An earlier update to show the location of working tree in the error |
||||
message did not consider the possibility that a git command may be |
||||
run in a bare repository, which has been corrected. |
||||
|
||||
* The "--recurse-submodules" option of various subcommands did not |
||||
work well when run in an alternate worktree, which has been |
||||
corrected. |
||||
|
||||
* Running "git rm" on a submodule failed unnecessarily when |
||||
.gitmodules is only cache-dirty, which has been corrected. |
||||
|
||||
* "git rebase -i" identifies existing commits in its todo file with |
||||
their abbreviated object name, which could become ambigous as it |
||||
goes to create new commits, and has a mechanism to avoid ambiguity |
||||
in the main part of its execution. A few other cases however were |
||||
not covered by the protection against ambiguity, which has been |
||||
corrected. |
||||
|
||||
* The index-pack code now diagnoses a bad input packstream that |
||||
records the same object twice when it is used as delta base; the |
||||
code used to declare a software bug when encountering such an |
||||
input, but it is an input error. |
||||
|
||||
* The code to automatically shrink the fan-out in the notes tree had |
||||
an off-by-one bug, which has been killed. |
||||
|
||||
* "git check-ignore" did not work when the given path is explicitly |
||||
marked as not ignored with a negative entry in the .gitignore file. |
||||
|
||||
* The merge-recursive machinery failed to refresh the cache entry for |
||||
a merge result in a couple of places, resulting in an unnecessary |
||||
merge failure, which has been fixed. |
||||
|
||||
* Fix for a bug revealed by a recent change to make the protocol v2 |
||||
the default. |
||||
|
||||
* "git merge signed-tag" while lacking the public key started to say |
||||
"No signature", which was utterly wrong. This regression has been |
||||
reverted. |
||||
|
||||
* MinGW's poll() emulation has been improved. |
||||
|
||||
* "git show" and others gave an object name in raw format in its |
||||
error output, which has been corrected to give it in hex. |
||||
|
||||
* Both "git ls-remote -h" and "git grep -h" give short usage help, |
||||
like any other Git subcommand, but it is not unreasonable to expect |
||||
that the former would behave the same as "git ls-remote --head" |
||||
(there is no other sensible behaviour for the latter). The |
||||
documentation has been updated in an attempt to clarify this. |
||||
|
||||
Also contains various documentation updates, code clean-ups and minor fixups. |
||||
Loading…
Reference in new issue