From: David Aguilar <davvid@gmail.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Allow to override mergetool.prompt with $GIT_MERGETOOL*_PROMPT
Date: Wed, 20 Jan 2010 23:44:28 -0800 [thread overview]
Message-ID: <20100121074427.GA26973@gmail.com> (raw)
In-Reply-To: <4B572192.2020606@gmail.com>
Hi,
On Wed, Jan 20, 2010 at 04:30:26PM +0100, Sebastian Schuberth wrote:
> This is for symmetry with git-difftool, and to make should_prompt_merge ()
> reusable from within git-difftool--helper.
>
> Signed-off-by: Sebastian Schuberth <sschuberth@gmail.com>
> ---
> git-mergetool--lib.sh | 9 +++++++++
> git-mergetool.sh | 3 ++-
> 2 files changed, 11 insertions(+), 1 deletions(-)
>
> diff --git a/git-mergetool--lib.sh b/git-mergetool--lib.sh
> index 5b62785..16b0343 100644
> --- a/git-mergetool--lib.sh
> +++ b/git-mergetool--lib.sh
> @@ -7,6 +7,15 @@ merge_mode() {
> test "$TOOL_MODE" = merge
> }
>
> +should_prompt_merge () {
> + local prompt=$(git config --bool mergetool.prompt || echo true)
> + if test "$prompt" = true; then
> + test -z "$GIT_MERGETOOL_NO_PROMPT"
> + else
> + test -n "$GIT_MERGETOOL_PROMPT"
> + fi
> +}
Someone already mentioned dropping "local" here.
The GIT_DIFFTOOL*_PROMPT variables are implementation details
about how git-difftool passes options to git-difftool--helper.
We don't advertise them in the documentation so we probably
shouldn't support them aside from what is needed for
git-difftool. We can drop this part.
61ed71dc just recently removed git-difftool--helper's use of
GIT_MERGE_TOOL based on this rationale.
> diff --git a/git-mergetool.sh b/git-mergetool.sh
> index b52a741..d453cb0 100755
> --- a/git-mergetool.sh
> +++ b/git-mergetool.sh
> @@ -202,7 +202,8 @@ merge_file () {
> return 0
> }
>
> -prompt=$(git config --bool mergetool.prompt || echo true)
> +should_prompt_merge
> +prompt=$?
>
> while test $# != 0
> do
git-difftool falling back to mergetool.prompt when
difftool.prompt is not available is good, especially
since we advertise that feature.
Once you drop the local declarations and the env. variable
it should be good to go. Patch v2, soon?
--
David
next prev parent reply other threads:[~2010-01-21 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 15:30 [PATCH 1/2] Allow to override mergetool.prompt with $GIT_MERGETOOL*_PROMPT Sebastian Schuberth
2010-01-20 15:59 ` Johannes Sixt
2010-01-20 16:10 ` Sebastian Schuberth
2010-01-21 7:44 ` David Aguilar [this message]
2010-01-21 10:10 ` Sebastian Schuberth
2010-01-22 1:58 ` 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=20100121074427.GA26973@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--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 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).