summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-05-25 11:36:25 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-05-25 11:36:25 -0700
commit4f64464023d0bf7ce065f1dccaf267ca38b3521f (patch)
tree0a4e42e08c200ab448c9879528e7662e1b8c52ce /Documentation/RelNotes
parentSync with maint (diff)
parentGit 1.7.10.3 (diff)
downloadtgif-4f64464023d0bf7ce065f1dccaf267ca38b3521f.tar.xz
Sync with 1.7.10.3
Diffstat (limited to 'Documentation/RelNotes')
-rw-r--r--Documentation/RelNotes/1.7.10.3.txt19
1 files changed, 15 insertions, 4 deletions
diff --git a/Documentation/RelNotes/1.7.10.3.txt b/Documentation/RelNotes/1.7.10.3.txt
index 153bf14032..703fbf1d60 100644
--- a/Documentation/RelNotes/1.7.10.3.txt
+++ b/Documentation/RelNotes/1.7.10.3.txt
@@ -6,10 +6,6 @@ Fixes since v1.7.10.2
* The message file for German translation has been updated a bit.
- * "git status --porcelain" ignored "--branch" option by mistake. The
- output for "git status --branch -z" was also incorrect and did not
- terminate the record for the current branch name with NUL as asked.
-
* Running "git checkout" on an unborn branch used to corrupt HEAD.
* When checking out another commit from an already detached state, we
@@ -21,6 +17,9 @@ Fixes since v1.7.10.2
"checkout" phase; when run without any "--quiet" option, it should
give progress to the lengthy operation.
+ * The directory path used in "git diff --no-index", when it recurses
+ down, was broken with a recent update after v1.7.10.1 release.
+
* "log -z --pretty=tformat:..." did not terminate each record with
NUL. The fix is not entirely correct when the output also asks for
--patch and/or --stat, though.
@@ -29,4 +28,16 @@ Fixes since v1.7.10.2
broken and gave undue precedence to configured log.date, causing
"git stash list" to show "stash@{time stamp string}".
+ * "git status --porcelain" ignored "--branch" option by mistake. The
+ output for "git status --branch -z" was also incorrect and did not
+ terminate the record for the current branch name with NUL as asked.
+
+ * When a submodule repository uses alternate object store mechanism,
+ some commands that were started from the superproject did not
+ notice it and failed with "No such object" errors. The subcommands
+ of "git submodule" command that recursed into the submodule in a
+ separate process were OK; only the ones that cheated and peeked
+ directly into the submodule's repository from the primary process
+ were affected.
+
Also contains minor fixes and documentation updates.