Re: [PATCH] Add 'git format-patch --to=' option and 'format.to' configuration variable.
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 17, 2010, 08:14 UTC
- Message-ID
- <7vhbpg5lf0.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <alpine.LNX.2.00.1002171706290.5479@vqena.qenxr.bet.am>
Steven Drake <sdrake@xnet.co.nz> writes:
Show 9 quoted lines
> On Tue, 16 Feb 2010, Junio C Hamano wrote: >> 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. > > $ ./git-format-patch --stdout master~5..master~1 >>~/mail/postponed-msgs > $ alpine -I cp > > Only problem with doing that is that alpine changes the Date: and > Message-Id: header (the later being a pain if I used --threaded).
Finally. That is the kind of "how somebody would work with format-patch output" I was looking for. Thanks.
> ... I would understand if you wanted to deprecate '--cc' from > format-patch and 'format.cc' (maybe keep it for backwards compat).
No, you took me wrong. Deprecation wasn't what I was after.
I wanted to see ways to _positively_ explain what format.{cc,to} are good for. With them, we can eventually have a few examples in EXAMPLES section of the manual page to help users (hint, hint...).