From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934083AbcBDKTz (ORCPT ); Thu, 4 Feb 2016 05:19:55 -0500 Received: from canardo.mork.no ([148.122.252.1]:44462 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933282AbcBDKTw convert rfc822-to-8bit (ORCPT ); Thu, 4 Feb 2016 05:19:52 -0500 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: "Steinar H. Gunderson" Cc: Felipe Balbi , Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, stern@rowland.harvard.edu Subject: Re: [PATCH v2] Add support for usbfs zerocopy. Organization: m References: <20160106001143.GA1171@kroah.com> <20160124211208.GA8696@kroah.com> <20160125080352.GA30907@imap.gmail.com> <20160203212317.GA7506@kroah.com> <20160203220911.GA1675@imap.gmail.com> <878u31phih.fsf@ti.com> <20160203234035.GA3533@imap.gmail.com> Date: Thu, 04 Feb 2016 11:17:26 +0100 In-Reply-To: <20160203234035.GA3533@imap.gmail.com> (Steinar H. Gunderson's message of "Thu, 4 Feb 2016 00:40:39 +0100") Message-ID: <87lh704w5l.fsf@nemi.mork.no> User-Agent: Gnus/5.130013 (Ma Gnus v0.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Steinar H. Gunderson" 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@bar.com --cc bar@foo.com --in-reply-to=abcd-message-id@foo.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