From: Johannes Sixt <j.sixt@viscovery.net>
Date: Tue, 13 Oct 2009 07:45:06 GMT
Subject: Re: [PATCH] bisect reset: Allow resetting to any commit, not just a branch
Message-ID: <4AD43002.5080003@viscovery.net>
In-Reply-To: <7v3a5n3hgn.fsf@alter.siamese.dyndns.org>

Junio C Hamano schrieb:
> Half of the time, the commit you test in your "git bisect" section would
> be a "good" one, and immediately after you tell it "bisect good", it tells
> you that some _other_ commit you marked "bad" is the first bad commit.  In
> such a case, you won't be on the commit that the bisect has found.

Oh, yes, very true; but it is very close. But the commit that git bisect
reset warps me to is perhaps 1000 steps in history away. I certainly do
not want to go there, ever, because I want to go back near the bad commit
right away. (Think of fewer files changed means less build time.) If git
bisect reset would check out the bad commit, this would be *very* convenient.

-- Hannes