summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2021-10-14 09:55:16 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-10-14 09:55:16 -0700
commitf443b226ca681d87a3a31e245a70e6bc2769123c (patch)
tree2299f60e8df63f285d1a9e02a31e92fc9ab9c4e3
parentMerge branch 'ja/doc-status-types-and-copies' (diff)
downloadtgif-f443b226ca681d87a3a31e245a70e6bc2769123c.tar.xz
Thirteenth batch
Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/RelNotes/2.34.0.txt22
1 files changed, 22 insertions, 0 deletions
diff --git a/Documentation/RelNotes/2.34.0.txt b/Documentation/RelNotes/2.34.0.txt
index 080687f202..0bfeaea546 100644
--- a/Documentation/RelNotes/2.34.0.txt
+++ b/Documentation/RelNotes/2.34.0.txt
@@ -62,6 +62,10 @@ UI, Workflows & Features
* The ref iteration code used to optionally allow dangling refs to be
shown, which has been tightened up.
+ * "git add", "git mv", and "git rm" have been adjusted to avoid
+ updating paths outside of the sparse-checkout definition unless
+ the user specifies a "--sparse" option.
+
Performance, Internal Implementation, Development Support etc.
@@ -146,6 +150,21 @@ Performance, Internal Implementation, Development Support etc.
* CI learns to run the leak sanitizer builds.
+ * "git grep --recurse-submodules" takes trees and blobs from the
+ submodule repository, but the textconv settings when processing a
+ blob from the submodule is not taken from the submodule repository.
+ A test is added to demonstrate the issue, without fixing it.
+
+ * Teach "git help -c" into helping the command line completion of
+ configuration variables.
+
+ * When "git cmd -h" shows more than one line of usage text (e.g.
+ the cmd subcommand may take sub-sub-command), parse-options API
+ learned to align these lines, even across i18n/l10n.
+
+ * Prevent "make sparse" from running for the source files that
+ haven't been modified.
+
Fixes since v2.33
-----------------
@@ -275,6 +294,9 @@ Fixes since v2.33
* Protocol v0 clients can get stuck parsing a malformed feature line.
+ * A few kinds of changes "git status" can show were not documented.
+ (merge d2a534c515 ja/doc-status-types-and-copies later to maint).
+
* Other code cleanup, docfix, build fix, etc.
(merge f188160be9 ab/bundle-remove-verbose-option later to maint).
(merge 8c6b4332b4 rs/close-pack-leakfix later to maint).