From: Johannes Schindelin Date: Tue, 24 Jun 2008 14:17:18 GMT Subject: [TOY PATCH] git bisect: introduce 'fixed' and 'unfixed' Message-ID: When you look for a fix instead of a regression, it can be quite hard to twist your brain into choosing the correct bisect command between 'git bisect bad' and 'git bisect good'. So introduce the commands 'git bisect fixed' and 'git bisect unfixed'. Signed-off-by: Johannes Schindelin --- When Randal talked about this on IRC, I laughed. But I just had the case where it took me _three_ attempts at a bisection, only to give up and write this patchlet. May it help someone else, too. git-bisect.sh | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/git-bisect.sh b/git-bisect.sh index 8b11107..d833e21 100755 --- a/git-bisect.sh +++ b/git-bisect.sh @@ -501,6 +501,8 @@ case "$#" in *) cmd="$1" shift + test $cmd = fixed && cmd=bad + test $cmd = unfixed && cmd=good case "$cmd" in help) git bisect -h ;; -- 1.5.6.127.g3fb9f