Re: [PATCH 3/3] notmuch: Add support for listing the parent message

diff --git a/b2/c186a84bd823056a06b9a0edde26189b784e73 b/b2/c186a84bd823056a06b9a0edde26189b784e73
new file mode 100644 (file)
index 0000000..6240b2a
--- /dev/null
+++ b/b2/c186a84bd823056a06b9a0edde26189b784e73
@@ -0,0 +1,80 @@
+Return-Path: <dme@dme.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id CD24A40D14B\r
+       for <notmuch@notmuchmail.org>; Thu,  4 Nov 2010 06:25:16 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.9\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5\r
+       tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001]\r
+       autolearn=unavailable\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id DVnliU6fjv5b for <notmuch@notmuchmail.org>;\r
+       Thu,  4 Nov 2010 06:24:56 -0700 (PDT)\r
+Received: from mail-ww0-f41.google.com (mail-ww0-f41.google.com\r
+ [74.125.82.41])       by olra.theworths.org (Postfix) with ESMTP id 988464196F0       for\r
+ <notmuch@notmuchmail.org>; Thu,  4 Nov 2010 06:24:56 -0700 (PDT)\r
+Received: by wwi18 with SMTP id 18so396030wwi.2\r
+       for <notmuch@notmuchmail.org>; Thu, 04 Nov 2010 06:24:55 -0700 (PDT)\r
+Received: by 10.227.157.11 with SMTP id z11mr726809wbw.122.1288877093985;\r
+       Thu, 04 Nov 2010 06:24:53 -0700 (PDT)\r
+Received: from ut.hh.sledj.net (host81-149-164-25.in-addr.btopenworld.com\r
+       [81.149.164.25])\r
+       by mx.google.com with ESMTPS id h29sm8555501wbc.3.2010.11.04.06.24.52\r
+       (version=TLSv1/SSLv3 cipher=RC4-MD5);\r
+       Thu, 04 Nov 2010 06:24:53 -0700 (PDT)\r
+Received: by ut.hh.sledj.net (Postfix, from userid 1000)\r
+       id 1061259405B; Thu,  4 Nov 2010 13:24:31 +0000 (GMT)\r
+To: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>\r
+Subject: Re: [PATCH 3/3] notmuch: Add support for listing the parent message\r
+In-Reply-To: <m3zktpbcjs.fsf@linux.vnet.ibm.com>\r
+References: <1288200417-6584-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>\r
+       <1288200417-6584-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com>\r
+       <87hbfx4euv.fsf@ut.hh.sledj.net>\r
+       <m3zktpbcjs.fsf@linux.vnet.ibm.com>\r
+User-Agent: Notmuch/0.4 (http://notmuchmail.org) Emacs/23.2.1\r
+       (x86_64-pc-linux-gnu)\r
+From: David Edmondson <dme@dme.org>\r
+Date: Thu, 04 Nov 2010 13:24:30 +0000\r
+Message-ID: <87eib143xt.fsf@ut.hh.sledj.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 04 Nov 2010 13:25:17 -0000\r
+\r
+On Thu, 04 Nov 2010 16:06:39 +0530, "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com> wrote:\r
+> On Thu, 04 Nov 2010 09:28:40 +0000, David Edmondson <dme@dme.org> wrote:\r
+> > On Wed, 27 Oct 2010 22:56:57 +0530, "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> wrote:\r
+> > > From: Aneesh Kumar K.V <aneesh.kumar@gmail.com>\r
+> > > \r
+> > > When you have long thread, it would be nice to be able to\r
+> > > show the message to which the current message is a reply\r
+> > \r
+> > The patch fires up a new search, destroying my context. Shouldn't the\r
+> > parent message be visible in the current thread and, if so, perhaps just\r
+> > searching in the current buffer for it (and jumping back there) be\r
+> > possible? (Maybe even with a key to pop back to the child easily.)\r
+> > \r
+> \r
+> It should actually stack up. That is, it fires up a new search but then a\r
+> 'q' should bring back the old context. One of the thing i really\r
+> wanted to keep was the ability to go back to the old context with a key\r
+> binding which in this case is achieved by 'q'\r
+\r
+I played some more and I agree, it's fine as is.\r