Re: [PATCH] Add 'git format-patch --to=' option and 'format.to' configuration variable.

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 17, 2010, 01:13 UTC
Message-ID: <7vhbpgpsto.fsf@alter.siamese.dyndns.org>
In-Reply-To: <alpine.LNX.2.00.1002171238310.2477@vqena.qenxr.bet.am>

Steven Drake <sdrake@xnet.co.nz> writes:

> Has the same functionality as the '--cc' option and 'format.cc'
> configuration variable but for the "To:" email header.  Half of the code to
> support this was already there.

I don't _mind_ adding such a config (I didn't check the patch text, though), but one thing I don't understand is what kind of workflow do people who use format.cc, format.to, --cc and --to are using.

My impression has always been that you drive your _MUA_ to set these values, and MUAs are either (1) not so cooperating to read these headers from format-patch output and use them to decide where to send mails from, 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.

How are you sending your output from format-patch, and how does having To: and Cc: header pregenerated by format-patch help you?