git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] merge-recursive: configurable 'merge' program
Date: Tue, 5 Dec 2006 16:01:50 +0100	[thread overview]
Message-ID: <200612051601.50784.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612051540230.28348@wbgn013.biozentrum.uni-wuerzburg.de>

Dnia wtorek 5. grudnia 2006 15:48, Johannes Schindelin napisał:
> 
> 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

      reply	other threads:[~2006-12-05 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 11:36 [PATCH] merge-recursive: configurable 'merge' program Sam Vilain
2006-12-05  0:01 ` Jakub Narebski
2006-12-05  7:38   ` Johannes Schindelin
2006-12-05 10:23     ` Jakub Narebski
2006-12-05 14:07       ` Johannes Schindelin
2006-12-05 14:26         ` Jakub Narebski
2006-12-05 14:48           ` Johannes Schindelin
2006-12-05 15:01             ` Jakub Narebski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200612051601.50784.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).