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

Re: git bisect with history manipulation

From
Linus Torvalds <torvalds@osdl.org>
Date
Oct 23, 2006, 15:59 UTC
Message-ID
<Pine.LNX.4.64.0610230855260.3962@g5.osdl.org>
In-Reply-To
<ehinsa$a7n$1@sea.gmane.org>
On Mon, 23 Oct 2006, Jakub Narebski wrote:
> 
> 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.
Oooh. 
Yeah, it's a great idea, but likely not practical (or even possible).

git-rebase really wants a linear set of patches to rebase, which you definitely don't have for that big history. In fact, even if rebase did the full history rebasing, if later history did a merge of an earlier thing (ie if the patch-series that you're trying to rebase onto was based on something that wasn't an "epoch tip", but that was in the middle of intertwined history), you'd really be screwed.

Also, let's face it, rebasing isn't _that_ fast. So trying to rebase huge swaths of code would be painful as hell, even if it was a nice linear series.

But yes, for simpler situations, you could try to switch the problem around like you suggest.

		Linus
Previous: Jakub NarebskiNext: Sean
Message 4 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.