From: Andreas Ericsson <ae@op5.se>
To: Charles Bailey <charles@hashpling.org>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
William Pursell <bill.pursell@gmail.com>,
Junio C Hamano <gitster@pobox.com>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH 2/3] Add -n/--no-prompt option to mergetool
Date: Tue, 21 Oct 2008 13:49:30 +0200 [thread overview]
Message-ID: <48FDC1CA.2080800@op5.se> (raw)
In-Reply-To: <1224583999-26279-2-git-send-email-charles@hashpling.org>
Charles Bailey wrote:
> This option lets git mergetool invoke the conflict resolution program
> without waiting for a user response each time.
>
> Also added a mergetool.prompt (default true) configuration variable
> controlling the same behaviour.
>
> Signed-off-by: Charles Bailey <charles@hashpling.org>
> ---
> Documentation/config.txt | 3 +++
> Documentation/git-mergetool.txt | 11 ++++++++++-
> git-mergetool.sh | 16 +++++++++++++---
> 3 files changed, 26 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index 29369d0..b4e4ee4 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -976,6 +976,9 @@ mergetool.keepBackup::
> is set to `false` then this file is not preserved. Defaults to
> `true` (i.e. keep the backup files).
>
> +mergetool.prompt::
> + Prompt before each invocation of the merge resolution program.
> +
> pack.window::
> The size of the window used by linkgit:git-pack-objects[1] when no
> window size is given on the command line. Defaults to 10.
> diff --git a/Documentation/git-mergetool.txt b/Documentation/git-mergetool.txt
> index e0b2703..6d6bfe0 100644
> --- a/Documentation/git-mergetool.txt
> +++ b/Documentation/git-mergetool.txt
> @@ -7,7 +7,7 @@ git-mergetool - Run merge conflict resolution tools to resolve merge conflicts
>
> SYNOPSIS
> --------
> -'git mergetool' [--tool=<tool>] [<file>]...
> +'git mergetool' [--tool=<tool>] [-n|--no-prompt|--prompt] [<file>]...
>
> DESCRIPTION
> -----------
> @@ -60,6 +60,15 @@ variable `mergetool.<tool>.trustExitCode` can be set to `true`.
> Otherwise, 'git-mergetool' will prompt the user to indicate the
> success of the resolution after the custom tool has exited.
>
> +-n or --no-prompt::
> + Don't prompt before each invocation of the merge resolution
> + program.
> +
There is discussion already about "-n should be for dry-run!" and git's
inconsistencies in such matters. Wouldn't -y ("assume yes on prompt")
be better?
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-10-21 11:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 10:13 [PATCH 1/3] Fix some tab/space inconsistencies in git-mergetool.sh Charles Bailey
2008-10-21 10:13 ` [PATCH 2/3] Add -n/--no-prompt option to mergetool Charles Bailey
2008-10-21 10:13 ` [PATCH 3/3] Add -k/--keep-going " Charles Bailey
2008-10-21 11:12 ` Jeff King
2008-10-21 11:49 ` Andreas Ericsson [this message]
2008-10-21 12:26 ` [PATCH 2/3] Add -n/--no-prompt " Charles Bailey
2008-10-22 21:17 ` Charles Bailey
2008-10-22 23:21 ` Junio C Hamano
2008-10-23 6:44 ` Charles Bailey
2008-10-24 22:32 ` William Pursell
2008-10-24 22:55 ` Charles Bailey
2008-10-25 10:11 ` William Pursell
2008-11-13 12:28 ` Charles Bailey
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=48FDC1CA.2080800@op5.se \
--to=ae@op5.se \
--cc=bill.pursell@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=tytso@mit.edu \
/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).