Steven Drake <sdrake@xxxxxxxxxx> writes:
> 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...).
--
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