From: Junio C Hamano <gitster@pobox.com>
To: Tim Henigan <tim.henigan@gmail.com>
Cc: git@vger.kernel.org, davvid@gmail.com
Subject: Re: [PATCH v2] mergetools: add support for DeltaWalker
Date: Fri, 02 Mar 2012 14:39:38 -0800 [thread overview]
Message-ID: <7vaa3ybpat.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1330694867-7601-1-git-send-email-tim.henigan@gmail.com> (Tim Henigan's message of "Fri, 2 Mar 2012 08:27:47 -0500")
Tim Henigan <tim.henigan@gmail.com> writes:
> mergetools/DeltaWalker | 12 ++++++++++++
How does an end user choose to use this backend? Perhaps like this?
$ git mergetool --tool=DeltaWalker
All the other files in mergetools/ are in lower case, and I _strongly_
prefer to have this new file also be in lower case.
Such a change may mean you may have to override translate_merge_tool_path
in this file, like some other backends seem to do.
> 1 file changed, 12 insertions(+)
> create mode 100644 mergetools/DeltaWalker
>
> diff --git a/mergetools/DeltaWalker b/mergetools/DeltaWalker
> new file mode 100644
> index 0000000..b9e6618
> --- /dev/null
> +++ b/mergetools/DeltaWalker
> @@ -0,0 +1,12 @@
> +diff_cmd () {
> + "$merge_tool_path" "$LOCAL" "$REMOTE" >/dev/null 2>&1
> +}
> +
> +merge_cmd () {
> + if $base_present
> + then
> + "$merge_tool_path" "$LOCAL" "$REMOTE" "$BASE" -merged="$PWD/$MERGED"
> + else
> + "$merge_tool_path" "$LOCAL" "$REMOTE" -merged="$PWD/$MERGED"
> + fi >/dev/null 2>&1
> +}
next prev parent reply other threads:[~2012-03-02 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 13:27 [PATCH v2] mergetools: add support for DeltaWalker Tim Henigan
2012-03-02 22:39 ` Junio C Hamano [this message]
2012-03-03 22:00 ` David Aguilar
2012-03-03 22:47 ` Junio C Hamano
2012-03-04 3:50 ` Tim Henigan
2012-03-05 2:10 ` David Aguilar
2012-03-05 2:38 ` Junio C Hamano
2012-03-05 14:22 ` Tim Henigan
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=7vaa3ybpat.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=tim.henigan@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 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).