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

Re: [PATCH] merge-recursive: configurable 'merge' program

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 5, 2006, 15:01 UTC
Message-ID
<200612051601.50784.jnareb@gmail.com>
In-Reply-To
<Pine.LNX.4.63.0612051540230.28348@wbgn013.biozentrum.uni-wuerzburg.de>
Dnia wtorek 5. grudnia 2006 15:48, Johannes Schindelin napisał:
Show 13 quoted lines
> 
> On Tue, 5 Dec 2006, Jakub Narebski wrote:
>
>> Hmmm... would it be possible to use xdl_merge() for recursion, and 
>> graphical merge tool for result? <Checks out earlier discussion>. I 
>> think yes, because of exposing xdl_merge() in git-merge-onefile...
> 
> In "next", only git-merge-recursive is converted to use xdl_merge(), and 
> it did not use git-merge-one-file to begin with. Since this is a shell 
> script (with a different syntax than merge), it would have to be converted 
> to a C builtin first. But feasible: git-merge-one-file takes 7 parameters, 
> the first 3 being SHA1s or empty strings. "merge" takes 3 filenames, with 
> possibly up to three "-L <name>" pairs before them.

I thought that Junio implemented (but perhaps not published) some script, I thought that was git-merge-onefile with some non-standard options, to function as replacement for RCS' merge, or Diffutils diff3.

Guess I was wrong (at least there is nothing I can find in pu about this).
-- 
Jakub Narebski
Previous: Johannes Schindelin
Message 8 of 8 in “merge-recursive: configurable 'merge' program”
  1. merge-recursive: configurable 'merge' programSam Vilain, Dec 4, 2006
  2. Jakub NarebskiDec 5, 2006
  3. Johannes SchindelinDec 5, 2006
  4. Jakub NarebskiDec 5, 2006
  5. Johannes SchindelinDec 5, 2006
  6. Jakub NarebskiDec 5, 2006
  7. Johannes SchindelinDec 5, 2006
  8. Jakub NarebskiDec 5, 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.