Fourteenth batch
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Sep 9, 2020 at 13:52 UTC
54e85e7af1ac9e9a92888060d6811ae767fea1bc
1 file changed
+28
Documentation/RelNotes/2.29.0.txt
+28
@@ -55,6 +55,15 @@ UI, Workflows & Features
55
object names of blobs involved in the patch, but its length was not
56
affected by the --abbrev option. Now it is.
57
58
+ * "git worktree" gained a "repair" subcommand to help users recover
59
+ after moving the worktrees or repository manually without telling
60
+ Git. Also, "git init --separate-git-dir" no longer corrupts
61
+ administrative data related to linked worktrees.
62
+
63
+ * The "--format=" option to the "for-each-ref" command and friends
64
+ learned a few more tricks, e.g. the ":short" suffix that applies to
65
+ "objectname" now also can be used for "parent", "tree", etc.
66
+
67
68
Performance, Internal Implementation, Development Support etc.
69
@@ -128,6 +137,14 @@ Performance, Internal Implementation, Development Support etc.
137
execute the git subcommands, especially built-ins, in "git-foo"
138
form, which have been corrected.
139
140
+ * When a packfile is removed by "git repack", multi-pack-index gets
141
+ cleared; the code was taught to do so less aggressively by first
142
+ checking if the midx actually refers to a pack that no longer
143
+ exists.
144
+
145
+ * Internal API clean-up to handle two options "diff-index" and "log"
146
+ have, which happen to share the same short form, more sensibly.
147
+
148
149
Fixes since v2.28
150
-----------------
@@ -286,6 +303,16 @@ Fixes since v2.28
303
been freed, which has been fixed.
304
(merge 6479ea4a8a jk/xrealloc-avoid-use-after-free later to maint).
305
306
+ * "git status" has trouble showing where it came from by interpreting
307
+ reflog entries that recordcertain events, e.g. "checkout @{u}", and
308
+ gives a hard/fatal error. Even though it inherently is impossible
309
+ to give a correct answer because the reflog entries lose some
310
+ information (e.g. "@{u}" does not record what branch the user was
311
+ on hence which branch 'the upstream' needs to be computed, and even
312
+ if the record were available, the relationship between branches may
313
+ have changed), at least hide the error to allow "status" show its
314
+ output.
315
+
316
* Other code cleanup, docfix, build fix, etc.
317
(merge 84544f2ea3 sk/typofixes later to maint).
318
(merge b17f411ab5 ar/help-guides-doc later to maint).
@@ -311,3 +338,4 @@ Fixes since v2.28
338
(merge ee22a29215 so/pretty-abbrev-doc later to maint).
339
(merge 3100fd5588 jc/post-checkout-doc later to maint).
340
(merge 17bae89476 pb/doc-external-diff-env later to maint).
341
+ (merge 27ed6ccc12 jk/worktree-check-clean-leakfix later to maint).