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

RE: Problem with git bisect between 2.6.15 and 2.6.16

From
Luck, Tony <tony.luck@intel.com>
Date
Mar 29, 2006, 19:43 UTC
Message-ID
<B8E391BBE9FE384DAA4C5C003888BE6F06176441@scsmsx401.amr.corp.intel.com>
Show 7 quoted lines
> This was progressing fine until I ran into an issue that makes the kernel unstable causing
> it to crash at semi-random times.  I'm down to about 350 commits left in the bisect.  I've
> tried:
> 
> git reset --hard HEAD~3
>
>no luck, same problem, unstable

You can try "git bisect visualize" to invoke gitk on the remaining commits, and then pick a likely looking stable point for your next test. This is documented reasonably well in the git Documentation/howto/isolate-bugs-with-bisect.txt

-Tony
Message 1 of 1 in “RE: Problem with git bisect between 2.6.15 and 2.6.16”
  1. Luck, TonyMar 29, 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.