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

Re: [PATCH] Document 'git bisect fix'.

From
YDYann Dirson <dirson@bertin.fr>
Date
Mar 16, 2011, 13:34 UTC
Message-ID
<20110316143402.69e66f16@chalon.bertin.fr>
Show 8 quoted lines
>I'd say the replace method is perfect for transporting an existing fix
>"back in time" when the range of non-bisectable commits is limited. But
>since you have to replace the right (most recent) commit in that range
>it is less convenient when you have a fix due to a changed/exotic build
>environment or such which you do not want in your mainline.
>
>Also, you have to rebase the whole history back to the commit which
>introduced the problem

Right, and that makes it much more difficult when you want to be selective about which fixes you want to apply.

-- 
Yann Dirson - Bertin Technologies
Message 1 of 1 in “Re: [PATCH] Document 'git bisect fix'.”
  1. Yann DirsonMar 16, 2011

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.