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

Re: git-bisect doesnt record bad commits

From
OHOlaf Hering <olh@suse.de>
Date
Feb 6, 2006, 22:24 UTC
Message-ID
<20060206222448.GA9196@suse.de>
In-Reply-To
<Pine.LNX.4.64.0602061417510.3854@g5.osdl.org>
 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
Previous: Linus Torvalds
Message 3 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.