Samuel GROOT <samuel.gr...@grenoble-inp.org> writes: > 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.
I'm not sure this is right. I'd typically configure gmane in my user-wide config file, so I'd have it configured all the time, but I may not always want to fetch from it (e.g. replying to a message which is not on a mailing-list, or if gmane is down, or ...). Fetching by default would clearly work in most cases, but for the few remaning cases it may be painful for the user if the only way to disable fetching is to remove the configuration from the config file. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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
