From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755536AbcBCXks (ORCPT ); Wed, 3 Feb 2016 18:40:48 -0500 Received: from mail-wm0-f54.google.com ([74.125.82.54]:38814 "EHLO mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752279AbcBCXkn (ORCPT ); Wed, 3 Feb 2016 18:40:43 -0500 Date: Thu, 4 Feb 2016 00:40:39 +0100 From: "Steinar H. Gunderson" To: Felipe Balbi Cc: 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. Message-ID: <20160203234035.GA3533@imap.gmail.com> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <878u31phih.fsf@ti.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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). /* Steinar */ -- Software Engineer, Google Switzerland