Re: git bisect enhancements?

From: Junio C Hamano <junkio@cox.net>
Date: Nov 30, 2005, 22:23 UTC
Message-ID: <7vmzjlojw6.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <1133388429.30767.37.camel@cashmere.sps.mot.com>

Jon Loeliger <jdl@freescale.com> writes:

Show 5 quoted lines

> Sure.  But I'm proposing to alter the new bisection
> middle point.  I don't know its status yet.  I am
> just angling on hedging my bets of a "good midpoint"
> choice by finding something that is likely to be
> more stable than the proposed midpoint.

You could "git reset --hard <that-commit-N-up-or-down>", compile, test and say "git bisect good" or "git bisect bad".

Even "N commits before" is not so easy. "git reset --hard bisect~2" would be 2 commits before what git-bisect suggested as long as that chain in question is a single strand of pearls. "N commits after" is a bit harder, especially when a merge is involved. But you are right. Bisect should be able to do what you can visually do with gitk.