threads / rfc / 12770

[RFC] git-bisect unsure

Subject: [RFC] git-bisect unsure

## tl;dr

4 messages between Mar 18, 2008 and Mar 20, 2008.

replies: 3people: 4as markdown or json

Rhodes, Kate· Mar 18, 2008, 15:57 UTC · lore

I'm in the middle of tracking down a bug, unfortunately one of the commits that git-bisect chose had an unrelated problem in it that broke my build. As a result I don't know if this version is good or bad as far as the bug I'm trying to track down is concerned. I would think of a number of situations where one bug could interfere with the testing of another.

My proposal is to add an "unsure" option to git-bisect.

I'm thinking that when you say "git bisect unsure" it would simply shift one commit earlier or later and refrain from ever checking out one marked unsure until there were only "unsure" ones left at which point it would add a disclaimer when you called bad or good and throw up it's hands in frustration if you were to say "unsure" again.

-Kate

Junio C Hamano· Mar 20, 2008, 00:55 UTC · re: Rhodes, Kate · lore

Re: [RFC] git-bisect unsure

"Rhodes, Kate" <masukomi@gmail.com> writes:

Show 7 quoted lines

> My proposal is to add an "unsure" option to git-bisect.
>
> I'm thinking that when you say "git bisect unsure" it would simply
> shift one commit earlier or later and refrain from ever checking out
> one marked unsure until there were only "unsure" ones left at which
> point it would add a disclaimer when you called bad or good and throw
> up it's hands in frustration if you were to say "unsure" again.

Patches welcome.

^L

But if this is what you are trying to say:

    6ca8b97 (Bisect: add "skip" to the short usage string., 2007-10-29)

you are about 4.5 months late ;-).

Christian Couder· Mar 20, 2008, 07:51 UTC · re: Junio C Hamano · lore

Re: [RFC] git-bisect unsure

Le jeudi 20 mars 2008, Junio C Hamano a écrit :

Show 18 quoted lines

> "Rhodes, Kate" <masukomi@gmail.com> writes:
> > My proposal is to add an "unsure" option to git-bisect.
> >
> > I'm thinking that when you say "git bisect unsure" it would simply
> > shift one commit earlier or later and refrain from ever checking out
> > one marked unsure until there were only "unsure" ones left at which
> > point it would add a disclaimer when you called bad or good and throw
> > up it's hands in frustration if you were to say "unsure" again.
>
> Patches welcome.
>
> ^L
>
> But if this is what you are trying to say:
>
>     6ca8b97 (Bisect: add "skip" to the short usage string., 2007-10-29)
>
> you are about 4.5 months late ;-).

Yeah, it seems that "bisect skip" should do the job.

Thanks, Christian.

Jon Loeliger· Mar 20, 2008, 14:58 UTC · re: Junio C Hamano · lore

Re: [RFC] git-bisect unsure

On Wed, 2008-03-19 at 19:55, Junio C Hamano wrote:

Show 5 quoted lines

> But if this is what you are trying to say:
> 
>     6ca8b97 (Bisect: add "skip" to the short usage string., 2007-10-29)
> 
> you are about 4.5 months late ;-).

Heh. That and one can always nudget bisect to a different commit directly by hand as well.

jdl