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

diff --git a/57/2a6d79dd413b4985330563cad57526d7452c71 b/57/2a6d79dd413b4985330563cad57526d7452c71
new file mode 100644 (file)
index 0000000..a9cd568
--- /dev/null
+++ b/57/2a6d79dd413b4985330563cad57526d7452c71
@@ -0,0 +1,108 @@
+Return-Path: <jrollins@finestructure.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 E0C5E431FAF\r
+       for <notmuch@notmuchmail.org>; Tue,  3 Jul 2012 01:40:38 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.29\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] 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 HyHjuJLB6Hwh for <notmuch@notmuchmail.org>;\r
+       Tue,  3 Jul 2012 01:40:38 -0700 (PDT)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+       [131.215.239.19])\r
+       by olra.theworths.org (Postfix) with ESMTP id 78AE3431FAE\r
+       for <notmuch@notmuchmail.org>; Tue,  3 Jul 2012 01:40:38 -0700 (PDT)\r
+Received: from earth-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+       by earth-doxen-postvirus (Postfix) with ESMTP id 0984866E0026;\r
+       Tue,  3 Jul 2012 01:40:38 -0700 (PDT)\r
+X-Spam-Scanned: at Caltech-IMSS on earth-doxen by amavisd-new\r
+Received: from finestructure.net (unknown [76.89.192.57])\r
+       (Authenticated sender: jrollins)\r
+       by earth-doxen-submit (Postfix) with ESMTP id 21B0966E010C;\r
+       Tue,  3 Jul 2012 01:40:34 -0700 (PDT)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+       id C2CA675A; Tue,  3 Jul 2012 01:40:33 -0700 (PDT)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: Ethan <ethan.glasser.camp@gmail.com>,\r
+       Mark Walters <markwalters1009@gmail.com>\r
+Subject: Re: [RFC PATCH 00/14] modular mail stores based on URIs\r
+In-Reply-To:\r
+ <CAOJ+Ob0MSOez2MvD2fCgF7t32kFPk4g2+xCud88QmBLt_b5pOA@mail.gmail.com>\r
+References: <1340656899-5644-1-git-send-email-ethan@betacantrips.com>\r
+       <877gutnmf1.fsf@qmul.ac.uk>\r
+       <CAOJ+Ob0Kw0Kkhh9C27Xv9gvqtNowzQiNqrLAtvti7fL8NND2+w@mail.gmail.com>\r
+       <87k3yrmahu.fsf@qmul.ac.uk>\r
+       <CAOJ+Ob0MSOez2MvD2fCgF7t32kFPk4g2+xCud88QmBLt_b5pOA@mail.gmail.com>\r
+User-Agent: Notmuch/0.13.2+54~ga0426dc (http://notmuchmail.org) Emacs/23.4.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Tue, 03 Jul 2012 01:40:31 -0700\r
+Message-ID: <87obnx8cg0.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha256; protocol="application/pgp-signature"\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, 03 Jul 2012 08:40:39 -0000\r
+\r
+--=-=-=\r
+\r
+On Sun, Jul 01 2012, Ethan <ethan.glasser.camp@gmail.com> wrote:\r
+>> I wonder if the following would be practical: use // as the field\r
+>> separator:\r
+>>\r
+>> e.g. mbox://filename//start_of_message+length\r
+>>\r
+>> I think 2 consecutive slashes // is about the only thing we can assume\r
+>> is not in the path or filename. Since it is not in the filename I think\r
+>> parsing should be trivial (thus avoiding the extra library).\r
+>>\r
+>\r
+> Can you explain what you mean when you say that two consecutive slashes\r
+> can't appear in a URL? Ordinary filesystem paths can contain them, and so\r
+> can file: URLs. (I just looked up file:///home/ethan///////tmp and Firefox\r
+> handled that OK.)\r
+\r
+Does firefox resolve this as /home/ethan/tmp, or /home/ethan///////tmp?\r
+For me iceweasel resolves it as /home/jrollins/tmp.  I think this is\r
+might be the behavior to which Mark is referring.\r
+\r
+jamie.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.12 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJP8q//AAoJEO00zqvie6q8Ld8QALTmvwMrd/OnUlRezWjPAlQx\r
+5v33nIS+cdOqswrjJOlph4xgCkJNcU0DLj0EYrg30ISh1BjPilD7ugl64QzsKXwC\r
+NGgeYVARpQcFWSAjxmyUhAG7BocrPyLv1Wr8fQA1+CLgKTqYqMxXwhq5dpNkNDeW\r
+z6bKXv6rn2bSapRrlxULh25cVtwU5HHly+d1Cswax7KlNKX9UNdi+SiuA/2n5HKB\r
+Ya7i9M6jAF7m5UgrjGEyRk1OqIXUS3behnLW4223X+alzdEP7SCuYSJnz6kE17DW\r
+gYfuLAu78WKPM19dUkuQ/KWfggLJIK2MQea96Z3hWhGMKs3LZ0zz2mweYIa+oLT1\r
+JEx1idNmAYn0cEXHEu4AJsszntIWxu9N60TYXjn8vbhiTXQtb83C8R3EK9xYNHs6\r
+5p99BnU0zg7lsArRq+fYxEQb3E0PXhyfTsSu2cLKxb0SpfteF1rx0XNw8eoDxRhA\r
+meUBRHnSB4HqKzkyFpz3VZl2QTkvwC1lkAbAlOdpvbltydJMtls6mrNX1+UKgG07\r
+Lll0p3cLjINbO2VwlKHUhy70oc3vm/gSDTVo/IR1218Kl1gYuhCORuiubiFRSRQz\r
+OXZjUYdnI7C5MArWWnpws6/CreDnhTIpYA7JGpSkZIMhG+oK27EvqplYKw0M95N7\r
+MiutqLAFxGEfHbsDd0Fz\r
+=ZslS\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r