From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nanako Shiraishi <nanako3@lavabit.com>,
peff@peff.net, sam@vilain.net, git@vger.kernel.org,
paulus@samba.org, Markus Heidelberg <markus.heidelberg@web.de>,
Jay Soffian <jaysoffian@gmail.com>
Subject: Re: [PATCH] gitk: Use git-difftool for external diffs
Date: Wed, 30 Dec 2009 23:16:45 -0800 [thread overview]
Message-ID: <20091231071642.GA10067@gmail.com> (raw)
In-Reply-To: <7vy6kk52an.fsf@alter.siamese.dyndns.org>
On Tue, Dec 29, 2009 at 11:49:52PM -0800, Junio C Hamano wrote:
> Nanako Shiraishi <nanako3@lavabit.com> writes:
>
> > Junio, could you tell us what happened to this thread?
>
> See http://thread.gmane.org/gmane.comp.version-control.git/132983/focus=133414
>
> In short, the particular way to call difftool this patch implements was
> found to be inadequate to support existing external diff support by gitk
> and a small difftool update will happen first, followed by a patch to gitk
> to use the updated difftool, to avoid regression.
I started the first step:
http://thread.gmane.org/gmane.comp.version-control.git/135613
http://thread.gmane.org/gmane.comp.version-control.git/135613/focus=135612
The 2nd patch implements the the --gui option which Markus
pointed out would be needed to avoid issues such as calling
"vimdiff" from a console-less gitk:
http://article.gmane.org/gmane.comp.version-control.git/133386
I marked the --gui patch as "RFC" since it introduced a new
config variable and I want to make sure that we agreed on its
name. I didn't get any feedback about that patch
(my fault-- we were in RC freeze and I forgot to CC: Markus).
If that looks like a good first step then we can do the next
step which would be to introduce the --extcmd= option as
mentioned here:
http://thread.gmane.org/gmane.comp.version-control.git/132983/focus=133386
I will try and prepare the changes for --extcmd= within
the next week assuming the existing --gui patch is ok.
On a related note, Jay Soffian recently submitted a
git-mergetool--lib patch adding support for "diffmerge".
It made it clear that there were parts of git-mergetool--lib
that could use some refactoring:
http://thread.gmane.org/gmane.comp.version-control.git/134906
Jay did mention that he'd give it a shot at the time, though
it does seems like the refactoring could wait until we see
how --extcmd= fits into the world.
Thank you for following up on this thread, Nanako.
--
David
next prev parent reply other threads:[~2009-12-31 7:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 3:12 [PATCH] gitk: Use git-difftool for external diffs David Aguilar
2009-11-19 9:03 ` Paul Mackerras
2009-11-19 19:39 ` David Aguilar
2009-11-19 22:21 ` Paul Mackerras
2009-11-20 7:53 ` Junio C Hamano
2009-11-20 18:55 ` David Aguilar
2009-11-20 20:51 ` Junio C Hamano
2009-11-21 21:47 ` David Aguilar
2009-11-20 23:33 ` Markus Heidelberg
2009-12-30 3:13 ` Nanako Shiraishi
2009-12-30 7:49 ` Junio C Hamano
2009-12-31 7:16 ` David Aguilar [this message]
2009-12-31 20:37 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-03-27 21:45 David Aguilar
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=20091231071642.GA10067@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=markus.heidelberg@web.de \
--cc=nanako3@lavabit.com \
--cc=paulus@samba.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
/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).