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

Re: [PATCH] Use diff3 instead of merge in merge-recursive.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 18, 2006, 10:04 UTC
Message-ID
<Pine.LNX.4.63.0610181202260.14200@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<eh4sfr$3ej$1@sea.gmane.org>
Hi,
On Wed, 18 Oct 2006, Jakub Narebski wrote:
Show 11 quoted lines
> Uwe Zeisberger wrote:
> 
> > If no error occurs, merge (from rcs 5.7) is nothing but:
> > 
> >         diff3 -E -am -L label1 -L label2 -L label3 file1 file2 file3 > tmpfile
> >         cat tmpfile > file1
> > 
> > Using diff3 directly saves one fork per conflicting file.
> 
> Doesn't xdiff library git uses have diff3/merge equivalent?
> Couldn't we use that instead (on less dependency, better performance)?

We have only half of libxdiff, lacking the patch functionality. And AFAIUI the minimal implementation of diff3 in xdiff just uses a diff of the first pair on the third file (or some other order). So, it is not really a diff3/merge: it would fail in fairly trivial cases.

Ciao, Dscho

P.S.: Davide, correct me if I'm wrong.
Previous: Jakub NarebskiNext: Linus Torvalds
Message 3 of 8 in “Use diff3 instead of merge in merge-recursive.”
  1. Use diff3 instead of merge in merge-recursive.Uwe Zeisberger, Oct 18, 2006
  2. Jakub NarebskiOct 18, 2006
  3. Johannes SchindelinOct 18, 2006
  4. Linus TorvaldsOct 18, 2006
  5. Daniel BarkalowOct 19, 2006
  6. Johannes SchindelinOct 18, 2006
  7. Uwe ZeisbergerOct 20, 2006
  8. Johannes SchindelinOct 21, 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.