Re: git bisect enhancements?
- From
Jon Loeliger <jdl@freescale.com>
- Date
- Nov 30, 2005, 22:07 UTC
- Message-ID
- <1133388429.30767.37.camel@cashmere.sps.mot.com>
- In-Reply-To
- <7vu0dtokqp.fsf@assigned-by-dhcp.cox.net>
On Wed, 2005-11-30 at 16:04, Junio C Hamano wrote:
Show 15 quoted lines
> Jon Loeliger <jdl@freescale.com> writes: > > > ... I want to "bump" the bisect point > > up two commits and _then_ build. > > > > So, I'm proposing something like: > > > > $ git bisect bump +<n> > > $ git bisect bump -<n> > > > > To move the bisection point "up" or "down" a commit chain. > > Hmph. Doesn't "bisect good" or "bisect bad" let you explicitly > say which one is good or bad, instead of just taking what it > suggests as the next midpoint?
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.
jdl