On 05/25/2016 08:31 PM, Matthieu Moy wrote:
So, a possible UI would be:
git send-email --in-reply-to=<id> => just set In-Reply-To: field.
git send-email --in-reply-to=<file> => set In-Reply-To, To and Cc.
git send-email --in-reply-to=<file> --cite => in addition, add the
body of the message quoted with '> '.
git send-email --in-reply-to=<id> --fetch => fetch and do like <file>
using the default configuration for fetch.
We designed a similar UI, except for the --fetch option:
We wanted to try to fetch the email from a distant server (e.g. gmane)
if that server address was set in the config file, and populate the
To:/Cc: fields.
If the file cannot be downloaded, or server address not set, just fill
the Reply-to header.
Either way, display what was done with the message-id given (unless
--quiet is set, of course).
This leaves room for:
git send-email --in-reply-to=<id> --fetch=gmane => fetch from gmane
(details on how to fetch would be in the config file)
This UI wouldn't allow using a file to get only the message-id. But I'm
not sure this is an interesting use-case.
IMHO when you reply to a thread with a patch, it seems
counter-productive to reply without notifying (putting in To:/Cc:) the
original author and people involved in the thread.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
