From: Christian Couder <chriscool@tuxfamily.org>
Date: Wed, 27 May 2009 05:26:59 GMT
Subject: Re: RFE: "git bisect reverse"
Message-ID: <200905270726.59883.chriscool@tuxfamily.org>
In-Reply-To: <4A1CBF7A.3090708@zytor.com>

Le Wednesday 27 May 2009, H. Peter Anvin a écrit :
> Sam Vilain wrote:
> > Oh, yes.  And another thing: 'git bisect run' / 'git bisect skip'
> > doesn't do a very good job of skipping around broken commits (ie when
> > the script returns 126).  It just seems to move to the next one; it
> > would be much better IMHO to first try the commit 1/3rd of the way into
> > the range, then if that fails, the commit 2/3rd of the way through it,
> > etc.
>
> I posted about that last year:
>
> http://marc.info/?l=git&i=48F3DCEB.1060803@zytor.com
>
> At the time, git bisect was still done in the shell and it was deemed
> too difficult.

Yeah, this was also asked by Ingo, and yeah, I think it should be easier to 
do now that most of the "git bisect next" shell code has been ported to C.

I will try to have a look at it soon.

Best regards,
Christian.