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

Re: Real-life kernel debugging scenario

From
Wwa1ter@myrealbox.com <wa1ter@myrealbox.com>
Date
Nov 9, 2005, 17:40 UTC
Message-ID
<Pine.LNX.4.64.0511090901370.6744@x2.ybpnyarg>
In-Reply-To
<Pine.LNX.4.64.0511071721200.3247@g5.osdl.org>
On Mon, 7 Nov 2005, Linus Torvalds wrote:
[...]
> The way to use "git bisect" couldn't be easier.

I see that Junio just added your entire response to Documentation/howto/ isolate-bugs-with-bisect.txt where even I could manage to find it :o)

> Also, figure out the most recent known-good commit (usually the _previous_
> kernel you ran: and if you've only done a single "pull" in between, it
> will be ORIG_HEAD).

The built-in variable ORIG_HEAD isn't explained anywhere AFAICT, or at least it wasn't until today. Are there other such magic variables which might be useful for us to know about?

Previous: Linus TorvaldsNext: Jon Loeliger
Message 5 of 7 in “Real-life kernel debugging scenario”
  1. waltNov 8, 2005
  2. David LangNov 8, 2005
  3. Junio C HamanoNov 8, 2005
  4. Linus TorvaldsNov 8, 2005
  5. wa1ter@myrealbox.comNov 9, 2005
  6. Jon LoeligerNov 9, 2005
  7. Linus TorvaldsNov 9, 2005

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.