Re: [RFC/PATCH 0/3] use '--bisect-refs' as bisect rev machinery option

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 4, 2009, 21:52 UTC
Message-ID: <7vtyxaez4f.fsf@alter.siamese.dyndns.org>
In-Reply-To: <200911042226.25599.chriscool@tuxfamily.org>

Christian Couder <chriscool@tuxfamily.org> writes:

Show 10 quoted lines

> So to do that you would use "git bisect start ..." and then you could use:
>
> $ git rev-list --bisect HEAD --not $GOOD_COMMITS
>
> to get the commit that you would have to test if the current commit is bad 
> and:
>
> $ git rev-list --bisect  $BAD --not $GOOD_COMMITS HEAD
>
> to get the commit that you would have to test if the current commit is good.

Even in that case, the problem is still about narrowing the set of the current bisection graph. If --bisect option implicitly grabs good and bad defined in the refspace like Linus's patch does, it will give you the same behaviour of the above two commands, no?