Re: [notmuch] Missing messages breaking threads

diff --git a/0b/d7b5122b4559207ac195768d9384668e4325c6 b/0b/d7b5122b4559207ac195768d9384668e4325c6
new file mode 100644 (file)
index 0000000..341479f
--- /dev/null
+++ b/0b/d7b5122b4559207ac195768d9384668e4325c6
@@ -0,0 +1,88 @@
+Return-Path: <james@jameswestby.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 34564431FAE\r
+       for <notmuch@notmuchmail.org>; Fri, 18 Dec 2009 13:24:25 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\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 TZ3Pl9WNgIwv for <notmuch@notmuchmail.org>;\r
+       Fri, 18 Dec 2009 13:24:24 -0800 (PST)\r
+Received: from jameswestby.net (jameswestby.net [89.145.97.141])\r
+       by olra.theworths.org (Postfix) with ESMTP id DCA69431FBF\r
+       for <notmuch@notmuchmail.org>; Fri, 18 Dec 2009 13:24:23 -0800 (PST)\r
+Received: from cpc4-aztw22-2-0-cust59.aztw.cable.virginmedia.com\r
+       ([94.169.116.60] helo=flash)\r
+       by jameswestby.net with esmtpa (Exim 4.69)\r
+       (envelope-from <james@jameswestby.net>)\r
+       id 1NLkJC-0005zZ-Vr; Fri, 18 Dec 2009 21:24:23 +0000\r
+Received: by flash (Postfix, from userid 1000)\r
+       id 9155F6E546A; Fri, 18 Dec 2009 21:24:17 +0000 (GMT)\r
+From: James Westby <jw+debian@jameswestby.net>\r
+To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org\r
+In-Reply-To: <873a38ypg5.fsf@yoom.home.cworth.org>\r
+References: <87oclwrtqa.fsf@jameswestby.net>\r
+       <874onoysrl.fsf@yoom.home.cworth.org> <87my1grrdi.fsf@jameswestby.net>\r
+       <873a38ypg5.fsf@yoom.home.cworth.org>\r
+Date: Fri, 18 Dec 2009 21:24:17 +0000\r
+Message-ID: <87ljh0rn5q.fsf@jameswestby.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Subject: Re: [notmuch] Missing messages breaking threads\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.12\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: Fri, 18 Dec 2009 21:24:25 -0000\r
+\r
+On Fri, 18 Dec 2009 12:52:58 -0800, Carl Worth <cworth@cworth.org> wrote:\r
+> On Fri, 18 Dec 2009 19:53:13 +0000, James Westby <jw+debian@jameswestby.net> wrote:\r
+> Oh, I was assuming you wouldn't index any text. The UI can add "missing\r
+> message" for a document with no filename, for example.\r
+\r
+Works for me.\r
+\r
+> > So, to summarise, I should first look at storing filesizes, then\r
+> > the collision code to make it index further when the filesize grows,\r
+> > and then finally the code to add documents for missing messages?\r
+> \r
+> Some of the code areas to be touched will be changing soon, (at least as\r
+> far as when filenames appear and disappear). Hopefully I'll have\r
+> something posted for that sooner rather than later to avoid having to\r
+> redo too much work.\r
+\r
+That would be great. I'm learning all the code anyway, so there's not\r
+a whole lot of knowledge being thrown away.\r
+\r
+I've just sent an initial cut at the fist step.\r
+\r
+> > The only thing I am unclear on is how to handle existing databases?\r
+> > Do we have any concept of versioning? Or should I just assume that\r
+> > filesize: may not be in the document and act appropriately?\r
+> \r
+> My current, outstanding patch is going to be the first trigger for a\r
+> "flag day" where we'll all need to rewrite our databases.\r
+> \r
+> We don't have any concept of versioning yet, but it would obviously be\r
+> easy to have a new version document with an increasing integer.\r
+> \r
+> But even with my current patch I'm considering doing a graceful upgrade\r
+> of the database in-place rather than making the user do something like a\r
+> dump, delete, rebuild, restore. That would give a much better experience\r
+> than "Your database is out-of-date, please rebuild it", so we'll see if\r
+> I pursue that in the end.\r
+\r
+That sounds nice, I'd certainly prefer this sort of thing as it evolves.\r
+\r
+Thanks,\r
+\r
+James\r