Re: Displaying tags with many messages very slow in Emacs

diff --git a/f1/760733bcfa20e1a86aefd8317f44b359313b73 b/f1/760733bcfa20e1a86aefd8317f44b359313b73
new file mode 100644 (file)
index 0000000..bc4e2ee
--- /dev/null
+++ b/f1/760733bcfa20e1a86aefd8317f44b359313b73
@@ -0,0 +1,102 @@
+Return-Path: <webservice@bontempi.net>\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 9B12E431FD0\r
+       for <notmuch@notmuchmail.org>; Tue,  1 Nov 2011 06:36:46 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.001\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.001 tagged_above=-999 required=5\r
+       tests=[UNPARSEABLE_RELAY=0.001] autolearn=disabled\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 ntv8OP+p40wh for <notmuch@notmuchmail.org>;\r
+       Tue,  1 Nov 2011 06:36:46 -0700 (PDT)\r
+Received: from mail.forumcivico.org (mail.forumcivico.org [208.116.44.169])\r
+       by olra.theworths.org (Postfix) with ESMTP id F27A6431FB6\r
+       for <notmuch@notmuchmail.org>; Tue,  1 Nov 2011 06:36:45 -0700 (PDT)\r
+Received: from dummy.name; Tue, 01 Nov 2011 09:31:30 -0400\r
+Subject: Re: Displaying tags with many messages very slow in Emacs\r
+Mime-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+From: bnt <webservice@bontempi.net>\r
+X-Mailer: CommuniGate Pro WebUser v5.4.0\r
+In-Reply-To: <87bosx9fxr.fsf@gilead.invalid>\r
+Date: Tue, 1 Nov 2011 14:36:27 +0100\r
+Content-Transfer-Encoding: quoted-printable\r
+Message-Id: <109E7309-AA04-4252-B4ED-23B94A7AB2D8@bontempi.net>\r
+References: <B676D1F6-04DD-49A9-8284-5CF17D6C4602@bontempi.net>\r
+       <87fwi99vlj.fsf@wyzanski.jamesvasile.com>\r
+       <72587727-5371-4BFF-A21C-ECA11D2F7BB5@bontempi.net>\r
+       <87bosx9fxr.fsf@gilead.invalid>\r
+To: Daniel Schoepe <daniel@schoepe.org>\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: Tue, 01 Nov 2011 13:36:46 -0000\r
+\r
+\r
+On 2011, Oct 31, at 19:25 , Daniel Schoepe wrote:\r
+\r
+> On Mon, 31 Oct 2011 16:43:22 +0100, bnt <webservice@bontempi.net> =\r
+wrote:\r
+>> I am not too proficient with the patch utility. Is there some kind of\r
+>> scheduled git commits timeline?\r
+>=20\r
+> Unfortunately, there's a huge number of outstanding patches at the\r
+> moment, so it's impossible to say when/if it will be applied.\r
+>=20\r
+>> If not, I guess it will be a good time to learn patching.\r
+>=20\r
+> There's no need to use the patch binary directly when the patches are\r
+> sent in a format git understands, which is generally the case here. To\r
+> apply patches from a thread, you can use `git am patches.mbox' where\r
+> patches.mbox contains the mails with the patches.\r
+>=20\r
+> If you're using the emacs UI for notmuch, you can open only those\r
+> messages with the patches you want in a thread and pipe them to an =\r
+mbox\r
+> file like this:\r
+>=20\r
+> C-u | cat > ~/patches.mbox\r
+>=20\r
+> If there are no conflicts due to more recent changes to the =\r
+repository,\r
+> git am patches.mbox will apply them using the commit messages from the\r
+> mails.\r
+>=20\r
+> FWIW: There's another more recent series of patches that accomplishes =\r
+a\r
+> similar goal: id:"cover.1319833617.git.jani@nikula.org"\r
+>=20\r
+> Cheers,\r
+> Daniel\r
+\r
+\r
+Thank you so much for the explanation, and thanks to Jani for those =\r
+patches.\r
+\r
+I will work my way into applying them.\r
+\r
+As just a plain user, I was wondering if it would be possible to have a =\r
+"dev" or "untested" branch in the git repo, where one could just get all =\r
+the latest patches?=20\r
+\r
+Of course it would not be desirable if it would just complicate the =\r
+developers life.\r
+\r
+Thank you so much once again,\r
+\r
+Sam=\r