Steven Drake <sdrake@xxxxxxxxxx> writes: > I think it's weired to have an option & config variable for Cc and not To. This line in your message I agree with 100%, and I already said I do _not_ mind adding format.to or --to. But a sad thing is, this one line is the only one I agree with in your message. All the other lines including what your quoted in your message do not answer my question at all. Neither description by Daniel nor by Miklos explains how giving format.cc or --cc given to format-patch helps the user in the bigger picture. Is a user of this feature expected to always use send-email? If so, how is that different from giving these options to send-email instead? > Any MUA that does not cooperate with reading the To header is going to > give trouble with any header (e.g. Subject, Date). Yes, --cc/--to/format.cc/format.are not about helping users of these uncooperating MUAs, and that is perfectly fine. "It is bad that the feature does not to help them" is not what I am saying. I am only trying to find what these features are designed to help. If the set of MUAs that are helped by this feature is larger than "git send-email" by an iota, I'd be happy. >> or (2) is a git-send-email which is customizable already per repository so >> you do not have to do anything funky when running format-patch. > Haven't got around to using git-send-email yet! Then how would having To: and Cc: help in the format-patch output help you at all? I tried to ask you (apparently in a garbled grammar, sorry) what your workflow of sending the format-patch output to the outside world is. The reason why I am asking is _not_ because I want to reject this patch. I want to be able to explain to other people why it is beneficial to be able to specify to/cc setting to format-patch, and using it in what way in a larger picture it would help the user. I.e. saying "by setting format.to, your output will have these To: header" is not good enough, if we do not make it clear why having the "To/Cc" in the output helps users and in what way. I want to hear "because the output from format-patch has these To: header, your life gets easier *this way*, if the MUA you use to send out patches is ________. You can use command ______ of the MUA to read the whole thing including the headers, and you do not have to type nor remember the addresses; this is something you cannot do without using this feature if your favorite MUA is _______." If that MUA is "git send-email", then I would explain to my users "don't worry about these format-patch 'features'; if you are a user of "git send-email", then give them to that command instead." Feature duplication isn't a bad thing per-se, but I want to know about it. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html