Re: [PATCH] git-send-email: kill $prompting variable
- From
Jeff King <peff@peff.net>
- Date
- Aug 19, 2013, 21:25 UTC
- Message-ID
- <20130819212559.GB29258@sigill.intra.peff.net>
- In-Reply-To
- <1376674444-29599-1-git-send-email-rv@rasmusvillemoes.dk>
On Fri, Aug 16, 2013 at 05:34:04PM +0000, Rasmus Villemoes wrote:
Show 7 quoted lines
> The variable $prompting is weird. It is only read in one place (when > deciding whether to prompt for a Message-ID to use in In-Reply-To), > and it will be false unless we've taken the completely unrelated > branch filling in @initial_to. > > Prompting should be done if the info is needed, not if some unrelated > item had to be prompted for. So kill $prompting.
The prompting flag dates back to 1f038a0 from late 2005. I _think_ the intent was that you could use certain command lines to specify the required information (like initial compose subject line, sender, etc), and then send-email would skip prompting for the optional information (like in-reply-to). That makes it easier to use in a "batch" mode in which the user does not want to be prompted (they do not have to give a blank "--in-reply-to" to prevent the prompt).
Over the years, the set of items which triggered prompting (and which depended on previous prompts) has grown and shrunk, and most prompts do not respect the $prompting system at all. So I kind of doubt that anybody will care if it goes away; it does not make much sense at this point.
However, your patch will make the default be to ask about the initial message-id. Which is likely going to annoy people, as it is not necessary (and people who care can specify it on the command line). Would we want to get rid of it entirely?
-Peff