From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Brandon Williams <bmwill@google.com>, Jeff King <peff@peff.net>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [RFC PATCH] send-email: allow a custom hook to prevent sending email
Date: Sat, 10 Dec 2016 14:11:46 -0800 [thread overview]
Message-ID: <xmqqtwabo2n1.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAGZ79kZKify7VLfNp3FXXvc4UOGjdXfUaspNaeW0t5+hWc+cpw@mail.gmail.com> (Stefan Beller's message of "Fri, 9 Dec 2016 15:56:17 -0800")
Stefan Beller <sbeller@google.com> writes:
> On Fri, Dec 9, 2016 at 3:52 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Stefan Beller <sbeller@google.com> writes:
>>
>>> So you are suggesting to
>>> * have the check later in the game (e.g. just after asking
>>> "Send this email? ([y]es|[n]o|[q]uit|[a]ll): " as then other information
>>> such as additional @to @cc are available.
>>
>> Yeah, probably before the loop starts asking that question for each
>> message. And hook does not necessarily need to cause the program to
>> die. The question can be reworded to "Your hook says no, but do you
>> really want to send it?",
>
> You could, but...
Yes, "does not necessarily need to die" is different from "hence you
must avoid dying". Running the hook before you start the loop to
ask for each message merely makes it possible to avoid dying.
next prev parent reply other threads:[~2016-12-10 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 20:34 [RFC PATCH] send-email: allow a custom hook to prevent sending email Stefan Beller
2016-12-09 22:36 ` Junio C Hamano
2016-12-09 22:53 ` Stefan Beller
2016-12-09 23:52 ` Junio C Hamano
2016-12-09 23:56 ` Stefan Beller
2016-12-10 22:11 ` Junio C Hamano [this message]
2016-12-10 9:13 ` Jeff King
2016-12-12 19:35 ` Stefan Beller
2016-12-12 22:38 ` Junio C Hamano
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=xmqqtwabo2n1.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sbeller@google.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.