From: Sebastian Pipping <webmaster@hartwork.org>
To: David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add diffuse as merge and diff tool
Date: Mon, 30 Mar 2009 18:41:33 +0200 [thread overview]
Message-ID: <49D0F63D.2050205@hartwork.org> (raw)
In-Reply-To: <20090330045522.GA8308@gmail.com>
David Aguilar wrote:
>> Documentation/git-mergetool.txt | 3 ++-
>> Documentation/merge-config.txt | 7 ++++---
>> contrib/completion/git-completion.bash | 3 ++-
>> contrib/difftool/git-difftool-helper | 12 ++++++++----
>> contrib/difftool/git-difftool.txt | 4 ++--
>> git-gui/lib/mergetool.tcl | 7 +++++++
>> git-mergetool.sh | 15 ++++++++++++---
>> 7 files changed, 37 insertions(+), 14 deletions(-)
>
>
> Hey, thanks for the patch.
> Ouch.. too many places with duplicated information, huh?
Yes.
> I'm in the middle of refactoring git-(diff|merge)tool so that
> there is less duplication of code.
>
> Junio also has a number of difftool-related patches in his
> proposed-updates "pu" branch.
>
> Sebastian, would you mind if I rebased your patch on top of my
> work (once I send it out) so that it makes things easier on
> our kind maintainer? I have a big patch series coming down that
> does away with the redundancies so I think it'd be best if we
> transfered your changes on top of it. Would you mind if I
> rebased your patch and sent it out to the list?
>
> It wouldn't be until much later tonight (or tomorrow) at the
> earliest since I have some unpacking to take care of but if
> that's cool with you just let me know.
>
> You should see the refactoring patches from me shortly...
My patch is your patch, do as you please.
Just take care to keep the order of the files passed
to Diffuse intact, especially with $MERGED second,
as Diffuse sets focus on the second document after startup.
Sebastian
prev parent reply other threads:[~2009-03-30 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 22:25 [PATCH] Add diffuse as merge and diff tool Sebastian Pipping
2009-03-30 4:55 ` David Aguilar
2009-03-30 16:41 ` Sebastian Pipping [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=49D0F63D.2050205@hartwork.org \
--to=webmaster@hartwork.org \
--cc=davvid@gmail.com \
--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).