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

Re: git bisect with history manipulation

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 23, 2006, 15:42 UTC
Message-ID
<ehinsa$a7n$1@sea.gmane.org>
In-Reply-To
<Pine.LNX.4.64.0610230826080.3962@g5.osdl.org>
Linus Torvalds wrote:
> So depending on the problem, you can try two different approaches.

[The approaches being: 1) applying patchseries before testing, and marking the commit before applying as good or bad for bisect; 2) rebasing (applying) the patch-series on top of current kernel, and bisecting the series]

You can try yet another approach, namely rebase v2.6.15..v2.6.18 on top of your patch-series applied to v2.6.15, and bisect that.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Linus TorvaldsNext: Linus Torvalds
Message 3 of 8 in “git bisect with history manipulation”
  1. Kalle PokkiOct 23, 2006
  2. Linus TorvaldsOct 23, 2006
  3. Jakub NarebskiOct 23, 2006
  4. Linus TorvaldsOct 23, 2006
  5. SeanOct 23, 2006
  6. Jakub NarebskiOct 23, 2006
  7. SeanOct 23, 2006
  8. Catalin MarinasOct 23, 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.