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

Re: Merge made by recursive?

From
Jakub Narebski <jnareb@gmail.com>
Date
May 25, 2011, 18:04 UTC
Message-ID
<m339k2zmh8.fsf@localhost.localdomain>
In-Reply-To
<loom.20110525T192418-887@post.gmane.org>
Shawn Ligocki <sligocki@gmail.com> writes:
> Is this intentionally bad grammar? Every time I see it, I cringe a little. What 
> does it even mean? That it merged incrementally through each subsequent revision?

"Merge made by recursive" means "Merge made by 'recursive' merge strategy", where 'recursive' part refers to the fact that in case of criss-cross merge

        /--*---B1---M1---*---#  <-- foo
       /        \  /
   ---B           x
       \         / \
        \--*---B2---M2---*---#  <-- bar

(you are trying to merge 'bar' into 'foo') when we have more than one merge base, the strategy first creates synthetic merge for B1 and B2

                    M1---*---#  <-- foo
                   /
                  X
                   \
                    M2---*---#  <-- bar

and uses this X as a merge base for further merging. Or something like that.

See "Merge strategies" section in git-merge(1) documentation.
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: Ramkumar RamachandraNext: Junio C Hamano
Message 3 of 10 in “Merge made by recursive?”
  1. Shawn LigockiMay 25, 2011
  2. Ramkumar RamachandraMay 25, 2011
  3. Jakub NarebskiMay 25, 2011
  4. Junio C HamanoMay 25, 2011
  5. Jeff KingMay 25, 2011
  6. Junio C HamanoMay 25, 2011
  7. Junio C HamanoMay 25, 2011
  8. Jeff KingMay 25, 2011
  9. Jeff KingMay 25, 2011
  10. Jeff KingMay 25, 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.