git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-bisect doesnt record bad commits

From
OHOlaf Hering <olh@suse.de>
Date
Feb 6, 2006, 21:54 UTC
Message-ID
<20060206215442.GA12209@suse.de>

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
Next: Linus Torvalds
Message 1 of 3 in “git-bisect doesnt record bad commits”
  1. Olaf HeringFeb 6, 2006
  2. Linus TorvaldsFeb 6, 2006
  3. Olaf HeringFeb 6, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.