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

git bisect Vs branch

From
GRGrégory Romé <gregory.rome@maxim-ic.com>
Date
Oct 22, 2009, 15:48 UTC
Message-ID
<4AE07EEB.2010101@maxim-ic.com>

Considering the following story what is the method to find the regression with bisect?

I cloned a git repository (origin) which derives from another one (first-origin). A merge is done from first-origin to origin at each stable release (identified by a tag).

first-origin/master  *---A---------B-----------------------C-
                          \         \                       \     
origin/master              ----------B'----------U-----------C'-
                                      \           \           \   
master                                 ------------U'----------C''-

Now, after that I merged C' I fixed the conflicts and compiled without error but I have a regression. It could come from any commit between B and C or U and C', and I need to modify my code to correct the issue.

I would like to find the commit which introduce this regression by using git bisect but as the history is not linear it is not so easy (1). It though to create a linear history but I have no idea how to proceed...

Thanks, Grégory

(1) http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#bisect-merges

Next: Santi Béjar
Message 1 of 7 in “git bisect Vs branch”
  1. Grégory RoméOct 22, 2009
  2. Santi BéjarOct 22, 2009
  3. Grégory RoméOct 23, 2009
  4. Johannes SixtOct 23, 2009
  5. Grégory RoméOct 23, 2009
  6. Daniel BarkalowOct 23, 2009
  7. Junio C HamanoOct 23, 2009

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.