1 Return-Path: <dme@dme.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id DF2BF431FBD
\r
6 for <notmuch@notmuchmail.org>; Thu, 11 Feb 2010 00:00:40 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.001 tagged_above=-999 required=5
\r
12 tests=[BAYES_50=0.001] autolearn=ham
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id 8YQ-ie0cH-06 for <notmuch@notmuchmail.org>;
\r
16 Thu, 11 Feb 2010 00:00:40 -0800 (PST)
\r
17 Received: from mail-ew0-f220.google.com (mail-ew0-f220.google.com
\r
19 by olra.theworths.org (Postfix) with ESMTP id 22652431FAE
\r
20 for <notmuch@notmuchmail.org>; Thu, 11 Feb 2010 00:00:40 -0800 (PST)
\r
21 Received: by ewy20 with SMTP id 20so989234ewy.0
\r
22 for <notmuch@notmuchmail.org>; Thu, 11 Feb 2010 00:00:39 -0800 (PST)
\r
23 Received: by 10.213.15.14 with SMTP id i14mr1135090eba.83.1265875236841;
\r
24 Thu, 11 Feb 2010 00:00:36 -0800 (PST)
\r
25 Received: from aw.hh.sledj.net (host83-217-165-81.dsl.vispa.com
\r
27 by mx.google.com with ESMTPS id 28sm4742195eyg.20.2010.02.11.00.00.35
\r
28 (version=TLSv1/SSLv3 cipher=RC4-MD5);
\r
29 Thu, 11 Feb 2010 00:00:35 -0800 (PST)
\r
30 Received: by aw.hh.sledj.net (Postfix, from userid 1000)
\r
31 id 12BA53A03F; Thu, 11 Feb 2010 08:00:17 +0000 (GMT)
\r
32 From: David Edmondson <dme@dme.org>
\r
33 To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
\r
34 In-Reply-To: <877hqk4xr7.fsf@yoom.home.cworth.org>
\r
35 References: <87vde4derz.fsf@yoom.home.cworth.org>
\r
36 <877hqk4xr7.fsf@yoom.home.cworth.org>
\r
37 Date: Thu, 11 Feb 2010 08:00:16 +0000
\r
38 Message-ID: <87r5os5hin.fsf@aw.hh.sledj.net>
\r
40 Content-Type: text/plain; charset=us-ascii
\r
41 Subject: Re: [notmuch] emacs: On getting support for inline images
\r
42 X-BeenThere: notmuch@notmuchmail.org
\r
43 X-Mailman-Version: 2.1.13
\r
45 List-Id: "Use and development of the notmuch mail system."
\r
46 <notmuch.notmuchmail.org>
\r
47 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
49 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
50 List-Post: <mailto:notmuch@notmuchmail.org>
\r
51 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
52 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
54 X-List-Received-Date: Thu, 11 Feb 2010 08:00:41 -0000
\r
56 > PS. I know that attaching the output of "git format-patch" to a message
\r
57 > like this isn't the "git way". (That is, you won't get the right result
\r
58 > by simply piping this message to "git am".) But I really wish it
\r
59 > were. It seems I often write code in response to an email message and I
\r
60 > often want to reply to that *message* and incidentally provide a
\r
61 > patch. The git way, with the commit message in the subject and the first
\r
62 > part of the body seems backwards to me, (as far as the conversation is
\r
65 How about attaching a message/rfc822 part which contains the patch?
\r