Re: folder and path completely broken in HEAD?
authordm-list-email-notmuch <dm-list-email-notmuch@scs.stanford.edu>
Sat, 3 May 2014 15:55:56 +0000 (08:55 +1700)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 18:02:08 +0000 (10:02 -0800)
8d/651aec8ac13fe9f16c02eaede3528d9e22d022 [new file with mode: 0644]

diff --git a/8d/651aec8ac13fe9f16c02eaede3528d9e22d022 b/8d/651aec8ac13fe9f16c02eaede3528d9e22d022
new file mode 100644 (file)
index 0000000..356147b
--- /dev/null
@@ -0,0 +1,85 @@
+Return-Path:\r
+ <return-nerv6gmtbidcaxyx3prgnikhp6@temporary-address.scs.stanford.edu>\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 18B07431E64\r
+       for <notmuch@notmuchmail.org>; Sat,  3 May 2014 08:56:07 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] 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 mPQsSjWW9OWK for <notmuch@notmuchmail.org>;\r
+       Sat,  3 May 2014 08:56:03 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 989B4431FDA\r
+       for <notmuch@notmuchmail.org>; Sat,  3 May 2014 08:56:03 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (localhost.scs.stanford.edu\r
+ [127.0.0.1])  by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id\r
+ s43FtuTl013055;       Sat, 3 May 2014 08:55:56 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+       by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id s43Ftu9N000645;\r
+       Sat, 3 May 2014 08:55:56 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+       return-nerv6gmtbidcaxyx3prgnikhp6@ta.scs.stanford.edu using -f\r
+From: dm-list-email-notmuch@scs.stanford.edu\r
+To: Mark Walters <markwalters1009@gmail.com>, Jani Nikula <jani@nikula.org>\r
+Subject: Re: folder and path completely broken in HEAD?\r
+In-Reply-To: <87zjiz8hft.fsf@qmul.ac.uk>\r
+References: <87oazfo3w2.fsf@ta.scs.stanford.edu> <87zjiz8hft.fsf@qmul.ac.uk>\r
+Date: Sat, 03 May 2014 08:55:56 -0700\r
+Message-ID: <87iopmonzn.fsf@ta.scs.stanford.edu>\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
+Reply-To: David Mazieres expires 2014-08-01 PDT\r
+       <mazieres-kdhm6yewp4dq87x4tf5ix7eyxw@temporary-address.scs.stanford.edu>\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: Sat, 03 May 2014 15:56:07 -0000\r
+\r
+Mark Walters <markwalters1009@gmail.com> writes:\r
+\r
+>> All the way back.  Now you are saying there will be no convenient way to\r
+>> match just the "mail.class" part without the year?  How very\r
+>> distressing.  Ugh.\r
+>\r
+> Hi\r
+>\r
+> I am not quite sure what you are meaning by hierarchically group\r
+> messages. Searching for path:dir/foo/bar/** should give all messages in\r
+> all directories beneath dir/foo/bar. \r
+\r
+The problem is that the maildir++ spec disallows such pathnames.  If I\r
+need compatibility with maildir++ (for instance for an imap server), at\r
+least on a per-year basis, then my maildirs have to have names like:\r
+\r
+   2013/.foo.foo\r
+   2013/.foo.bar\r
+   2013/.foo.baz\r
+   2014/.foo.foo\r
+   2014/.foo.bar\r
+   2014/.foo.baz\r
+\r
+So if I want a way to aggregate all my foo mail in a single search,\r
+right now I just ask for folder:foo.  Will there be any equivalent in\r
+the new notmuch?\r
+\r
+Thanks,\r
+David\r