summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2013-10-23 13:36:57 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-10-23 13:36:57 -0700
commitea21efc74082da9453167773b658ea2439ab9bca (patch)
tree2f1129d9c8f279dc6dafb51ac522f34adc0b2f74 /Documentation/RelNotes
parentMerge branch 'bc/gnome-keyring' (diff)
parentAlmost 1.8.4.2 ;-) (diff)
downloadtgif-ea21efc74082da9453167773b658ea2439ab9bca.tar.xz
Sync with 'maint'
Diffstat (limited to 'Documentation/RelNotes')
-rw-r--r--Documentation/RelNotes/1.8.4.2.txt13
1 files changed, 13 insertions, 0 deletions
diff --git a/Documentation/RelNotes/1.8.4.2.txt b/Documentation/RelNotes/1.8.4.2.txt
index ebe5e68fcb..867ae69070 100644
--- a/Documentation/RelNotes/1.8.4.2.txt
+++ b/Documentation/RelNotes/1.8.4.2.txt
@@ -4,6 +4,19 @@ Git v1.8.4.2 Release Notes
Fixes since v1.8.4.1
--------------------
+ * "git branch --track" had a minor regression in v1.8.3.2 and later
+ that made it impossible to base your local work on anything but a
+ local branch of the upstream repository you are tracking from.
+
+ * "git ls-files -k" needs to crawl only the part of the working tree
+ that may overlap the paths in the index to find killed files, but
+ shared code with the logic to find all the untracked files, which
+ made it unnecessarily inefficient.
+
+ * When there is no sufficient overlap between old and new history
+ during a "git fetch" into a shallow repository, objects that the
+ sending side knows the receiving end has were unnecessarily sent.
+
* When running "fetch -q", a long silence while the sender side
computes the set of objects to send can be mistaken by proxies as
dropped connection. The server side has been taught to send a