From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id DF2BF431FBD for ; Thu, 11 Feb 2010 00:00:40 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] autolearn=ham Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8YQ-ie0cH-06 for ; Thu, 11 Feb 2010 00:00:40 -0800 (PST) Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com [209.85.219.220]) by olra.theworths.org (Postfix) with ESMTP id 22652431FAE for ; Thu, 11 Feb 2010 00:00:40 -0800 (PST) Received: by ewy20 with SMTP id 20so989234ewy.0 for ; Thu, 11 Feb 2010 00:00:39 -0800 (PST) Received: by 10.213.15.14 with SMTP id i14mr1135090eba.83.1265875236841; Thu, 11 Feb 2010 00:00:36 -0800 (PST) Received: from aw.hh.sledj.net (host83-217-165-81.dsl.vispa.com [83.217.165.81]) by mx.google.com with ESMTPS id 28sm4742195eyg.20.2010.02.11.00.00.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Feb 2010 00:00:35 -0800 (PST) Received: by aw.hh.sledj.net (Postfix, from userid 1000) id 12BA53A03F; Thu, 11 Feb 2010 08:00:17 +0000 (GMT) From: David Edmondson To: Carl Worth , notmuch@notmuchmail.org In-Reply-To: <877hqk4xr7.fsf@yoom.home.cworth.org> References: <87vde4derz.fsf@yoom.home.cworth.org> <877hqk4xr7.fsf@yoom.home.cworth.org> Date: Thu, 11 Feb 2010 08:00:16 +0000 Message-ID: <87r5os5hin.fsf@aw.hh.sledj.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: emacs: On getting support for inline images X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Feb 2010 08:00:41 -0000 > PS. I know that attaching the output of "git format-patch" to a message > like this isn't the "git way". (That is, you won't get the right result > by simply piping this message to "git am".) But I really wish it > were. It seems I often write code in response to an email message and I > often want to reply to that *message* and incidentally provide a > patch. The git way, with the commit message in the subject and the first > part of the body seems backwards to me, (as far as the conversation is > concerned). How about attaching a message/rfc822 part which contains the patch?