From: Junio C Hamano <gitster@pobox.com>
Date: Tue, 13 Oct 2009 07:21:50 GMT
Subject: Re: [PATCH] bisect reset: Allow resetting to any commit, not just a branch
Message-ID: <7vbpkb21yp.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4AD42203.6030802@viscovery.net>

Johannes Sixt <j.sixt@viscovery.net> writes:

> The situation that I'm faced quite frequently is that after I find a
> regression, I cannot tell which released version did not have the
> breakage. Hence, the first thing I have to do is to find a good commit.
> Therefore, I jump around in ancient history until I find a good commit.
> Then I start bisect. I certainly do NOT want to be warped back to this
> ancient commit by 'bisect reset'.

Unlike your other message, now, I can see _this_ one making sense very
much.

It is a very good explanation as to why BISECT_START (whose sole purpose
is to go back there) is not a very useful concept.  What you wrote deserve
to go to the "bisect reset" documentation to explain what the optional
<branch> argument (perhaps we would make it a <commit> with Anders's
patch) is good for and how it is intended to be used.