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

git bisect with history manipulation

From
KPKalle Pokki <kalle.pokki@iki.fi>
Date
Oct 23, 2006, 14:22 UTC
Message-ID
<a425f86c0610230722r2a0ae473o467d303f915b6c1e@mail.gmail.com>
In-Reply-To
<a425f86c0610230718i556537dei9a4b2a5fa8d7f003@mail.gmail.com>
Hi,

I'm still pretty new with git, and cannot quite figure out how to use "git bisect" effectively in this special case: I'm running an embedded powerpc board, to which I need about a dozen platform patches in the kernel. Originally I made the patches with quilt on top of 2.6.15.4. I recently started using git, and just applied the patches on top of v2.6.18. However, the system seems to oops at every boot now. So I did "git branch downgrade && git reset --hard v2.6.15" and applied my patches on top of it to create a starting state similar to what I had previously. There everything is ok.

Wanting to try to bisect the kernel versions, I then merged the master branch into the downgrade branch. Then I marked my last platform commit as good, and v2.6.18 as bad. However the bisect algorithm seems to group the platform patches near v2.6.18 instead of v2.6.15, since I don't have the platform files in the bisect checkout. And since I don't have the platform files, I can't compile a kernel that would run on my board.

So is there any way to insert a few patches to an arbitrary point backwards in time and start bisecting from that to the present time? Or am I thinking this somehow all wrong?

Next: Linus Torvalds
Message 1 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.