aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Schindelin <Johannes.Schindelin@gmx.de>2008-02-12 19:50:57 +0000
committerJunio C Hamano <gitster@pobox.com>2008-02-13 12:03:49 -0800
commitf454cdc48f31e64ceae2e8d4f4838349de2f5dee (patch)
tree51e625d344ef792fb378be2be0d8c63d69d8dcdb
parent8608b334343fd51f13e100f8f1a7a2788c13d6c5 (diff)
downloadgit-f454cdc48f31e64ceae2e8d4f4838349de2f5dee.tar.gz
git-f454cdc48f31e64ceae2e8d4f4838349de2f5dee.tar.xz
bisect: use verbatim commit subject in the bisect log
Due to a typo, the commit subject was shell expanded in the bisect log. That is, if you had some shell pattern in the commit subject, bisect would happily put all matching file names into the log. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Tested-by: Frans Pop <elendil@planet.nl> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rwxr-xr-xgit-bisect.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/git-bisect.sh b/git-bisect.sh
index 393fa3558..6594a6291 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -135,7 +135,7 @@ bisect_write() {
*) die "Bad bisect_write argument: $state" ;;
esac
git update-ref "refs/bisect/$tag" "$rev"
- echo "# $state: "$(git show-branch $rev) >>"$GIT_DIR/BISECT_LOG"
+ echo "# $state: $(git show-branch $rev)" >>"$GIT_DIR/BISECT_LOG"
test -z "$nolog" && echo "git-bisect $state $rev" >>"$GIT_DIR/BISECT_LOG"
}