From: Junio C Hamano <gitster@pobox.com>
To: Sebastian Schuberth <sschuberth@gmail.com>,
Pat Thoyts <patthoyts@users.sourceforge.net>
Cc: Olivier Croquette <ocroquette@free.fr>,
git@vger.kernel.org, David Aguilar <davvid@gmail.com>
Subject: Re: [PATCH] Copy mergetool "bc3" as "bc4"
Date: Mon, 20 Oct 2014 11:40:23 -0700 [thread overview]
Message-ID: <xmqqfvei37qg.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54455334.8000503@gmail.com> (Sebastian Schuberth's message of "Mon, 20 Oct 2014 20:23:48 +0200")
Sebastian Schuberth <sschuberth@gmail.com> writes:
>> Perhaps something like this, so that existing users can still use
>> "bc3" and other people can use "bc" if it bothers them that they
>> have to say "3" when the backend driver works with both 3 and 4?
>
> That indeed sounds like the best approach.
>
>> --- a/git-mergetool--lib.sh
>> +++ b/git-mergetool--lib.sh
>> @@ -250,7 +250,7 @@ list_merge_tool_candidates () {
>> tools="opendiff kdiff3 tkdiff xxdiff meld $tools"
>> fi
>> tools="$tools gvimdiff diffuse diffmerge ecmerge"
>> - tools="$tools p4merge araxis bc3 codecompare"
>> + tools="$tools p4merge araxis bc bc3 codecompare"
>
> Why keep bc3 here?
I didn't carefully look at the code that uses this list to see if we
have to list everything or can list just the ones we recommend, and
erred on the safer side (unlike the one for completion where I
omitted bc3 as "deprecated").
I'll let mergetools experts decide when rolling the final patch ;-)
> And shouldn't we update git-gui/lib/mergetool.tcl, too?
Yes we should, but git-gui is not in my bailiwick, and shouldn't be
done relative to my tree anyway. I'll Cc this message to Pat.
Thanks.
next prev parent reply other threads:[~2014-10-20 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 11:03 [PATCH] Copy mergetool "bc3" as "bc4" Olivier Croquette
2014-10-20 16:40 ` Junio C Hamano
2014-10-20 17:32 ` Junio C Hamano
2014-10-20 18:23 ` Sebastian Schuberth
2014-10-20 18:40 ` Junio C Hamano [this message]
2014-10-21 8:44 ` David Aguilar
2014-10-21 18:27 ` Junio C Hamano
2014-10-20 20:35 ` Olivier Croquette
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=xmqqfvei37qg.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=ocroquette@free.fr \
--cc=patthoyts@users.sourceforge.net \
--cc=sschuberth@gmail.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.