{"thread":{"id":"3752","subject":"RE: Problem with git bisect between 2.6.15 and 2.6.16","startedAt":"2006-03-29T19:43:20Z","lastAt":"2006-03-29T19:43:20Z","messageCount":1,"participants":["Luck, Tony"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"18131","messageId":"B8E391BBE9FE384DAA4C5C003888BE6F06176441@scsmsx401.amr.corp.intel.com","threadId":"3752","inReplyTo":null,"subject":"RE: Problem with git bisect between 2.6.15 and 2.6.16","fromName":"Luck, Tony","fromEmail":"tony.luck@intel.com","sentAt":"2006-03-29T19:43:20Z","receivedAt":"2006-03-29T19:43:20Z","isPatch":false,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":" \n> This was progressing fine until I ran into an issue that makes the kernel unstable causing\n> it to crash at semi-random times.  I'm down to about 350 commits left in the bisect.  I've\n> tried:\n> \n> git reset --hard HEAD~3\n>\n>no luck, same problem, unstable\n\nYou can try \"git bisect visualize\" to invoke gitk on the remaining commits, and\nthen pick a likely looking stable point for your next test.  This is documented\nreasonably well in the git Documentation/howto/isolate-bugs-with-bisect.txt\n\n-Tony\n"}]}