path: root/git-bisect-script
diff options
authorLinus Torvalds <>2005-08-30 18:04:39 (GMT)
committerJunio C Hamano <>2005-08-30 18:57:28 (GMT)
commit670f5fe34f0f6a363297d5dcd73051089b78fe82 (patch)
tree615d6a98d870d8822ce6cb5e2b61a18cf50ecb2e /git-bisect-script
parent61f01a5b773915402da37a34e706db56fe90b776 (diff)
[PATCH] Fix bisection terminating condition
When testing bisection and using gitk to visualize the result, it was obvious that the termination condition was broken. We know what the bad entry is only when the bisection ends up telling us to test the known-bad entry again. Also, add a safety net: if somebody marks as good something that includes the known-bad point, we now notice and complain, instead of writing an empty revision to the new bisection branch. Signed-off-by: Linus Torvalds <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'git-bisect-script')
1 files changed, 6 insertions, 2 deletions
diff --git a/git-bisect-script b/git-bisect-script
index 0c5c107..649b702 100755
--- a/git-bisect-script
+++ b/git-bisect-script
@@ -105,12 +105,16 @@ bisect_next() {
good=$(git-rev-parse --sq --revs-only --not \
$(cd "$GIT_DIR" && ls refs/bisect/good-*)) &&
rev=$(eval "git-rev-list --bisect $good $bad") || exit
- nr=$(eval "git-rev-list $rev $good" | wc -l) || exit
- if [ "$nr" -le "1" ]; then
+ if [ -z "$rev" ]; then
+ echo "$bad was both good and bad"
+ exit 1
+ fi
+ if [ "$rev" = "$bad" ]; then
echo "$rev is first bad commit"
git-diff-tree --pretty $rev
exit 0
+ nr=$(eval "git-rev-list $rev $good" | wc -l) || exit
echo "Bisecting: $nr revisions left to test after this"
echo "$rev" > "$GIT_DIR/refs/heads/new-bisect"
git checkout new-bisect || exit