Re: [RFC PATCH 00/14] modular mail stores based on URIs

diff --git a/d5/ce5276a12cbf73605da0fd0abcdfa1ae731a09 b/d5/ce5276a12cbf73605da0fd0abcdfa1ae731a09
new file mode 100644 (file)
index 0000000..ff34c59
--- /dev/null
+++ b/d5/ce5276a12cbf73605da0fd0abcdfa1ae731a09
@@ -0,0 +1,115 @@
+Return-Path: <ethan.glasser.camp@gmail.com>\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 806C7431FB6\r
+       for <notmuch@notmuchmail.org>; Thu, 28 Jun 2012 23:43:05 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.798\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.798 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7]\r
+       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 GRqhHwBP9nxI for <notmuch@notmuchmail.org>;\r
+       Thu, 28 Jun 2012 23:43:04 -0700 (PDT)\r
+Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com\r
+       [209.85.212.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id BDF67431FAF\r
+       for <notmuch@notmuchmail.org>; Thu, 28 Jun 2012 23:43:04 -0700 (PDT)\r
+Received: by vbbfc26 with SMTP id fc26so2425761vbb.26\r
+       for <notmuch@notmuchmail.org>; Thu, 28 Jun 2012 23:43:04 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
+       :cc:content-type;\r
+       bh=f+igHKmLBkJaGVzbX+/JokcAy7Ixy2ddI6yDlJThcLY=;\r
+       b=knddrBa8QJ+HYV2+vnS8Th8mfDrNi4QMbw3mJ78exagDTa09iIXE9gZaPkw9SNtEha\r
+       JraZ/h4CYdrR1sn4wbErwSd+JatmsJaTsORrKMvjC9q8g64tHzOHC/ISMjeouy8MmKnB\r
+       4+v0tB57NhJTs7FoWKU/ES1lAIZJujGMvFQeh1N06PDSzqchCkvoavF2YOxBbRB7t5QW\r
+       vOEHoDij0LGwmp+cDGZjOfZKjSNOBOwLpfYWBf7IDdpgx2zrtOCBUvkXHR6c6oxuSS+L\r
+       XCDifHBSmozCO0q7B3YcbAuFOdaQGa28q8v4M6Dali0hXmTw+5fzIUgcJNRfw868JdF6\r
+       cXBw==\r
+MIME-Version: 1.0\r
+Received: by 10.52.17.207 with SMTP id q15mr172738vdd.49.1340952184088; Thu,\r
+       28 Jun 2012 23:43:04 -0700 (PDT)\r
+Received: by 10.220.6.3 with HTTP; Thu, 28 Jun 2012 23:43:03 -0700 (PDT)\r
+In-Reply-To: <87bok3m70p.fsf@qmul.ac.uk>\r
+References: <1340656899-5644-1-git-send-email-ethan@betacantrips.com>\r
+       <87bok3m70p.fsf@qmul.ac.uk>\r
+Date: Fri, 29 Jun 2012 02:43:04 -0400\r
+Message-ID:\r
+ <CAOJ+Ob1bsbU2uj2F_7CZFY2t2Pu78whNETHTYfZVKPEaymGw8Q@mail.gmail.com>\r
+Subject: Re: [RFC PATCH 00/14] modular mail stores based on URIs\r
+From: Ethan <ethan.glasser.camp@gmail.com>\r
+To: Mark Walters <markwalters1009@gmail.com>\r
+Content-Type: multipart/alternative; boundary=bcaec5040a4c97e99b04c396c281\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: Fri, 29 Jun 2012 06:43:05 -0000\r
+\r
+--bcaec5040a4c97e99b04c396c281\r
+Content-Type: text/plain; charset=ISO-8859-1\r
+\r
+On Thu, Jun 28, 2012 at 6:00 PM, Mark Walters <markwalters1009@gmail.com>wrote:\r
+\r
+>\r
+> Just a quick question: does this update the database with\r
+> maildir://files URIs instead of just filenames? In other words is it\r
+> safe to try out on actual mailstores?\r
+>\r
+\r
+It doesn't change any of the existing filenames or do anything like a\r
+database "upgrade". If you run notmuch new, it should add a URI-based\r
+filename to each message, but I don't think it should remove old filenames,\r
+so I would expect it to be fine. But I didn't expect anyone to try it on\r
+their actual mail database.\r
+\r
+(I used it on a trial system but when I reverted to master some things\r
+> seemed to stop working)\r
+>\r
+\r
+Sorry for breaking it :)\r
+\r
+Ethan\r
+\r
+--bcaec5040a4c97e99b04c396c281\r
+Content-Type: text/html; charset=ISO-8859-1\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<div class=3D"gmail_quote">On Thu, Jun 28, 2012 at 6:00 PM, Mark Walters <s=\r
+pan dir=3D"ltr">&lt;<a href=3D"mailto:markwalters1009@gmail.com" target=3D"=\r
+_blank">markwalters1009@gmail.com</a>&gt;</span> wrote:<br><blockquote clas=\r
+s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=\r
+ding-left:1ex">\r
+<br>\r
+Just a quick question: does this update the database with<br>\r
+maildir://files URIs instead of just filenames? In other words is it<br>\r
+safe to try out on actual mailstores?<br></blockquote><div><br>It doesn&#39=\r
+;t change any of the existing filenames or do anything like a database &quo=\r
+t;upgrade&quot;. If you run notmuch new, it should add a URI-based filename=\r
+ to each message, but I don&#39;t think it should remove old filenames, so =\r
+I would expect it to be fine. But I didn&#39;t expect anyone to try it on t=\r
+heir actual mail database.<br>\r
+<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=\r
+ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">\r
+\r
+(I used it on a trial system but when I reverted to master some things<br>\r
+seemed to stop working)<br></blockquote><div><br>Sorry for breaking it :)<b=\r
+r><br>Ethan<br><br></div></div>\r
+\r
+--bcaec5040a4c97e99b04c396c281--\r