git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: William Pursell <bill.pursell@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] feature request: git-mergetool --force
Date: Sat, 18 Oct 2008 16:54:43 -0400	[thread overview]
Message-ID: <20081018205443.GA29534@coredump.intra.peff.net> (raw)
In-Reply-To: <48FA2E9F.3090305@gmail.com>

On Sat, Oct 18, 2008 at 07:44:47PM +0100, William Pursell wrote:

>> Something like --no-prompt makes more sense to me, though probably
>> something a little easier to type would be nice (or maybe alias "-n").
>
> Actually, perhaps an "interactive=no" configuration setting,
> which might imply trustExitCode = true.

That sounds reasonable to me.

-Peff

  reply	other threads:[~2008-10-18 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 23:23 [PATCH] feature request: git-mergetool --force William Pursell
2008-10-18 15:48 ` Jeff King
2008-10-18 18:44   ` William Pursell
2008-10-18 20:54     ` Jeff King [this message]
2008-10-18 23:16       ` Charles Bailey
2008-10-19 11:47         ` Jeff King

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=20081018205443.GA29534@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=bill.pursell@gmail.com \
    --cc=git@vger.kernel.org \
    /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).