[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lh704w5l.fsf@nemi.mork.no>
Date: Thu, 04 Feb 2016 11:17:26 +0100
From: Bjørn Mork <bjorn@...k.no>
To: "Steinar H. Gunderson" <sesse@...gle.com>
Cc: Felipe Balbi <balbi@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
stern@...land.harvard.edu
Subject: Re: [PATCH v2] Add support for usbfs zerocopy.
"Steinar H. Gunderson" <sesse@...gle.com> writes:
> On Thu, Feb 04, 2016 at 12:15:50AM +0200, Felipe Balbi wrote:
>>> Since I've now been bitten by this several times: Is there any sort of best
>>> practice for integrating git with MUAs? What I'm doing right now is
>>> cut-and-paste from mutt to get the to/cc/in-reply-to headers right, and
>>> that's suboptimal. It feels like it should be a FAQ, but I can't really find
>>> anything obvious.
>> have you tried git send-email ? If you wanna send as a reply to another
>> message, use:
>>
>> $ git send-email --to foo@....com --cc bar@....com --in-reply-to=abcd-message-id@....bar.com
>
> Unfortunately that doesn't change anything; I still need to cut-and-paste the
> to, cc and in-reply-to manually. What I'd want is something like
> “git send-email as a reply to the last email in my outbox”.
>
> Attaching the patch gives me exactly this, by the way, but seemingly ends up
> with a format that's more cumbersome to receive (which is a bad tradeoff).
Then use Mutt to reply, but include the patch inline instead of
attaching it. I believe this is discussed in the Mutt section of
Documentation/email-clients.txt
Bjørn
Powered by blists - more mailing lists