From: arjen@yaph.org (Arjen Laarhoven)
To: Junio C Hamano <junkio@cox.net>
Cc: tytso@mit.edu, git@vger.kernel.org
Subject: Re: [PATCH] Teach git-mergetool about Apple's opendiff/FileMerge
Date: Fri, 23 Mar 2007 09:25:01 +0100 [thread overview]
Message-ID: <20070323082501.GF3854@regex.yaph.org> (raw)
In-Reply-To: <7vbqiksh4a.fsf@assigned-by-dhcp.cox.net>
Hi,
> I cannot comment on the calling interface of opendiff, as I do
> not have access to an Apple. Here are my first impressions.
>
> > diff --git a/git-mergetool.sh b/git-mergetool.sh
> > index 7942fd0..58ae201 100755
> > --- a/git-mergetool.sh
> > +++ b/git-mergetool.sh
> > @@ -248,6 +248,30 @@ merge_file () {
> > mv -- "$BACKUP" "$path.orig"
> > fi
> > ;;
> > + opendiff)
> > + touch "$BACKUP"
> > + if base_present; then
> > + opendiff $LOCAL $REMOTE -ancestor $BASE -merge $path | cat
> > + else
> > + opendiff $LOCAL $REMOTE -merge $path | cat
> > + fi
>
> I sense inconsistent tabbing here.
Somehow I missed this.
> More seriously, all of the above $variable references must be
> dq'ed; see other case arms for good examples.
I don't use shell scripting much, some reading up on quoting
enlightened me :-)
> What's the purpose of this cat anyway? It looks like an
> expensive no-op to me.
opendiff is a wrapper for the FileMerge.app application. It launches the
FileMerge binary with the expanded filenames and returns immediately,
which is confusing, as git-mergetool immediately continues. When the
output of opendiff is piped somewhere, it'll wait until FileMerge is
exited (and the user has had a chance to save the merged file).
I think there is another solution, I'll look into this.
> > + if test "$path" -nt "$BACKUP" ; then
> > + status=0;
> > + else
> > + while true; do
> > + echo "$path seems unchanged."
> > + echo -n "Was the merge successful? [y/n] "
> > + read answer < /dev/tty
> > + case "$answer" in
> > + y*|Y*) status=0; break ;;
> > + n*|N*) status=1; break ;;
> > + esac
> > + done
> > + fi
> > + if test "$status" -eq 0; then
> > + mv -- "$BACKUP" "$path.orig"
> > + fi
> > + ;;
> > esac
>
> This part is duplicated across meld|vimdiff and xxdiff arms; you
> probably would want to have a patch that makes a shell function
> to factor this out, and then another patch to add this opendiff
> support.
Will do.
Arjen
next prev parent reply other threads:[~2007-03-23 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 21:37 [PATCH] Teach git-mergetool about Apple's opendiff/FileMerge Arjen Laarhoven
2007-03-23 4:45 ` Junio C Hamano
2007-03-23 4:52 ` Steven Grimm
2007-03-23 8:25 ` Arjen Laarhoven [this message]
2007-03-23 14:15 ` Theodore Tso
2007-03-23 18:42 ` Marco Roeland
2007-03-29 14:03 ` Theodore Tso
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=20070323082501.GF3854@regex.yaph.org \
--to=arjen@yaph.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tytso@mit.edu \
/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).