From: Linus Torvalds <torvalds@osdl.org>
Date: Mon, 06 Feb 2006 22:21:12 GMT
Subject: Re: git-bisect doesnt record bad commits
Message-ID: <Pine.LNX.4.64.0602061417510.3854@g5.osdl.org>
In-Reply-To: <20060206215442.GA12209@suse.de>



On Mon, 6 Feb 2006, Olaf Hering wrote:
> 
> Is there a reason why git-bisect does only record good ones? I would
> really like to know which commits did crash for me. :(

It does. Look in the bisection log (".git/BISECT_LOG").

Now, the reason it doesn't actually save them away as _tags_ is because 
technically, it doesn't need to. The algorithm itself only really cares 
about the most recently marked-bad commit, and the others are totally 
uninteresting from an algorithmic standpoint.

That said, if you want the visualization tools (for example) to show them, 
you could certainly _create_ the tags, if you want to. The fact that they 
wouldn't be used by the bisection algorithm doesn't mean that you can't 
create the ".git/refs/bisect/bad-<sha1>" file in _addition_ to the one 
that marks the latest one.

		Linus