From 62e91efafd2030b7dc33ac6450b4e9a316e6ecc6 Mon Sep 17 00:00:00 2001 From: John Keeping Date: Wed, 3 Jul 2013 19:27:39 +0100 Subject: [PATCH 1/2] git-config: update doc for --get with multiple values Since commit 00b347d (git-config: do not complain about duplicate entries, 2012-10-23), "git config --get" does not exit with an error if there are multiple values for the specified key but instead returns the last value. Update the documentation to reflect this. Signed-off-by: John Keeping Signed-off-by: Junio C Hamano --- Documentation/git-config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt index 9ae2508f3f..772ae2ac3f 100644 --- a/Documentation/git-config.txt +++ b/Documentation/git-config.txt @@ -82,7 +82,7 @@ OPTIONS --get:: Get the value for a given key (optionally filtered by a regex matching the value). Returns error code 1 if the key was not - found and error code 2 if multiple key values were found. + found and the last value if multiple key values were found. --get-all:: Like get, but does not fail if the number of values for the key From 81a199bb1cd483321962a7bfe5db33980bbf0f01 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 3 Jul 2013 15:43:41 -0700 Subject: [PATCH 2/2] Update draft release notes to 1.8.3.3 Signed-off-by: Junio C Hamano --- Documentation/RelNotes/1.8.3.3.txt | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/Documentation/RelNotes/1.8.3.3.txt b/Documentation/RelNotes/1.8.3.3.txt index 58a570ef3d..04289e793c 100644 --- a/Documentation/RelNotes/1.8.3.3.txt +++ b/Documentation/RelNotes/1.8.3.3.txt @@ -4,8 +4,23 @@ Git v1.8.3.3 Release Notes Fixes since v1.8.3.2 -------------------- + * "gitweb" forgot to clear a global variable $search_regexp upon each + request, mistakenly carrying over the previous search to a new one + when used as a persistent CGI. + + * The wildmatch engine did not honor WM_CASEFOLD option correctly. + + * "git log -c --follow $path" segfaulted upon hitting the commit that + renamed the $path being followed. + + * When a reflog notation is used for implicit "current branch", + e.g. "git log @{u}", we did not say which branch and worse said + "branch ''" in the error messages. + * Mac OS X does not like to write(2) more than INT_MAX number of bytes; work it around by chopping write(2) into smaller pieces. * Newer MacOS X encourages the programs to compile and link with their CommonCrypto, not with OpenSSL. + +Also contains various minor documentation updates.