From: David Aguilar <davvid@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Araxis in mergetool, was Re: What's cooking in git.git (May 2009, #03; Mon, 25)
Date: Mon, 25 May 2009 02:50:45 -0700 [thread overview]
Message-ID: <20090525095044.GA13411@gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0905251050050.4288@intel-tinevez-2-302>
On Mon, May 25, 2009 at 10:54:43AM +0200, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 25 May 2009, Junio C Hamano wrote:
>
> > * da/araxis-mergetool (Sun May 24 00:24:41 2009 +0000) 1 commit
> > + mergetool--lib: add support for araxis merge
> >
> > I admit that I feel certain distaste in supporting a closed tool, but we
> > already make things bearable for people on Windows; Araxis is no worse,
> > right?
>
> Well, I think it is the first closed-source tool that we support, and I
> would feel less unhappy if somebody reported back that she tested it and
> it works fine.
>
> For the future, it might be better if mergetool could be configured using
> /etc/gitconfig to call the merge helper properly. Then we would not need
> to clutter git.git with properietary stuff, but could just have the
> Windows-specific handling in Git for Windows.
I have the same reservations.
When I first picked up mergetool it supported ecmerge.
ecmerge is also closed which is why I reasoned that it was ok
to try and win over Windows users.
It should be possible to configure it today using
/etc/gitconfig, so we might be best served going down the
add-an-entry-to-the-git-wiki route next time; provided
Windows paths and shell-quoting doesn't drive us mad when
writing it, of course ;)
--
David
next prev parent reply other threads:[~2009-05-25 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 8:33 What's cooking in git.git (May 2009, #03; Mon, 25) Junio C Hamano
2009-05-25 8:54 ` Araxis in mergetool, was " Johannes Schindelin
2009-05-25 9:31 ` Wincent Colaiuta
2009-05-25 9:50 ` David Aguilar [this message]
2009-05-25 10:05 ` Michael Wookey
2009-05-25 22:23 ` Junio C Hamano
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=20090525095044.GA13411@gmail.com \
--to=davvid@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.