Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

From: Junio C Hamano <gitster@pobox.com>
Date: May 25, 2016, 18:15 UTC
Message-ID: <xmqqr3cqypg6.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <vpqeg8q5b6f.fsf@anie.imag.fr>

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

Show 6 quoted lines

> This should work, but sounds like too much of overloading of
> --in-reply-to IMHO: if given a message id, it would only add a reference
> to this message-id, but if given a file, it would also modify the To:
> and Cc: list.
>
> Not a strong objection, though.

Well, with your "that is the plan indeed", the option would behave the same whether given a message ID or a filename, no?

But I do agree that those who have accustomed to the behaviour of --in-reply-to that does not mess with To/Cc:, such a behaviour change is not desirable.

If we are adding a new --reply-to-email=<file|id>, it should behave as a superset of --in-reply-to (i.e. it should set In-Reply-to: using the message ID of the e-mail we are replying to), though.

Show 8 quoted lines

>> In the future, you might even teach send-email, perhaps via a user
>> configurable hook, a way to get to the message header and text given a
>> message-id, and when it happens, the same logic can be used when
>> --in-reply-to is given a message-id (i.e. you go from the id to the
>> message and find the addresses you would To/Cc: your message).
>
> That is the plan indeed. Fetching from gmane for example should be
> rather easy in perl, and would be really convenient!