Re: [PATCH] Documentation: bisect: "start" accepts one bad and many good commits

From: Junio C Hamano <junkio@cox.net>
Date: Apr 5, 2007, 04:55 UTC
Message-ID: <7vejmzxvwk.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070405053353.f4cebf57.chriscool@tuxfamily.org>

Christian Couder <chriscool@tuxfamily.org> writes:

> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>

Thanks.

Show 10 quoted lines

> +If you know beforehand more than one good commits, you can narrow the
> +bisect space down without doing the whole tree checkout every time you
> +give good commits. You give the bad revision immediately after `start`
> +and then you give all the good revisions you have:
> +
> +------------
> +$ git bisect start v2.6.20-rc6 v2.6.20-rc4 v2.6.20-rc1 --
> +                   # v2.6.20-rc6 is bad
> +                   # v2.6.20-rc4 and v2.6.20-rc1 are good
>  ------------

We would probably want mnemonic to help people remember the order of parameters: Bad comes before Good, simply because B sorts earlier than G.