threads / discuss / 3252

git-bisect doesnt record bad commits

Subject: git-bisect doesnt record bad commits

## tl;dr

3 messages between Feb 6, 2006 and Feb 6, 2006.

replies: 2people: 2as markdown or json

Olaf Hering· Feb 6, 2006, 21:54 UTC · lore

Is there a reason why git-bisect does only record good ones? I would really like to know which commits did crash for me. :(

 2006-02-05 14:07 .git/refs/bisect/good-a020ff412f0ecbb1e4aae1681b287e5785dd77b5
 2006-02-05 21:25 .git/refs/bisect/good-f61ea1b0c825a20a1826bb43a226387091934586
 2006-02-06 07:02 .git/refs/bisect/good-f2e46561cc1afa82b18b2fc6efc8510ec57c7d7d
 2006-02-06 10:24 .git/refs/bisect/good-d779188d2baf436e67fe8816fca2ef53d246900f
 2006-02-06 14:37 .git/refs/bisect/good-1cb9e8e01d2c73184e2074f37cd155b3c4fdaae6
 2006-02-06 17:43 .git/refs/bisect/good-54e08a2392e99ba9e48ce1060e0b52a39118419c
 2006-02-06 19:52 .git/refs/bisect/bad
 2006-02-06 21:57 .git/refs/bisect/good-4a4efbdee278b2f4ed91aad2db5c006ff754276e

-- 
short story of a lazy sysadmin:
 alias appserv=wotan

Linus Torvalds· Feb 6, 2006, 22:21 UTC · re: Olaf Hering · lore

Re: git-bisect doesnt record bad commits

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

Olaf Hering· Feb 6, 2006, 22:24 UTC · re: Linus Torvalds · lore

Re: git-bisect doesnt record bad commits

 On Mon, Feb 06, Linus Torvalds wrote:

Show 8 quoted lines

> 
> 
> 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").

Thats good enough for me to restore my steps, I think. Thanks.

-- 
short story of a lazy sysadmin:
 alias appserv=wotan