Re: [PATCH] TODO: date range queries - check
authorDavid Bremner <david@tethera.net>
Mon, 10 Dec 2012 12:35:51 +0000 (08:35 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:51:58 +0000 (09:51 -0800)
df/c9cdd1126f559019267a878c91fee84f5ca3d3 [new file with mode: 0644]

diff --git a/df/c9cdd1126f559019267a878c91fee84f5ca3d3 b/df/c9cdd1126f559019267a878c91fee84f5ca3d3
new file mode 100644 (file)
index 0000000..85e3c9a
--- /dev/null
@@ -0,0 +1,77 @@
+Return-Path: <bremner@unb.ca>\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 5A2A1431FBD\r
+       for <notmuch@notmuchmail.org>; Mon, 10 Dec 2012 04:36:02 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\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 wk0luljmKu+R for <notmuch@notmuchmail.org>;\r
+       Mon, 10 Dec 2012 04:36:01 -0800 (PST)\r
+Received: from tesseract.cs.unb.ca (tesseract.cs.unb.ca [131.202.240.238])\r
+       (using TLSv1 with cipher AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id DB6EC431FAF\r
+       for <notmuch@notmuchmail.org>; Mon, 10 Dec 2012 04:36:01 -0800 (PST)\r
+Received: from fctnnbsc30w-142167090129.dhcp-dynamic.fibreop.nb.bellaliant.net\r
+       ([142.167.90.129] helo=zancas.localnet)\r
+       by tesseract.cs.unb.ca with esmtpsa\r
+       (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1Ti2aS-00083Z-MQ; Mon, 10 Dec 2012 08:35:56 -0400\r
+Received: from bremner by zancas.localnet with local (Exim 4.80)\r
+       (envelope-from <bremner@unb.ca>)\r
+       id 1Ti2aN-0001Is-4s; Mon, 10 Dec 2012 08:35:51 -0400\r
+From: David Bremner <david@tethera.net>\r
+To: Tomi Ollila <tomi.ollila@iki.fi>, Jani Nikula <jani@nikula.org>,\r
+       Jameson Graef Rollins <jrollins@finestructure.net>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH] TODO: date range queries - check\r
+In-Reply-To: <m2wqws9ejj.fsf@guru.guru-group.fi>\r
+References: <1354833276-6219-1-git-send-email-jani@nikula.org>\r
+       <877gouine4.fsf@servo.finestructure.net>\r
+       <871uf2ukat.fsf@zancas.localnet>\r
+       <877gothkzw.fsf@servo.finestructure.net>\r
+       <87624dzgso.fsf@nikula.org>\r
+       <87boe5fsdn.fsf@servo.finestructure.net>\r
+       <87r4n0smot.fsf@zancas.localnet>\r
+       <871uf0fdnh.fsf@servo.finestructure.net>\r
+       <87sj7gp43x.fsf@nikula.org> <m2wqws9ejj.fsf@guru.guru-group.fi>\r
+User-Agent: Notmuch/0.14+163~g11a220a (http://notmuchmail.org) Emacs/24.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Mon, 10 Dec 2012 08:35:51 -0400\r
+Message-ID: <87hanuqe3c.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-Spam_bar: -\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: Mon, 10 Dec 2012 12:36:02 -0000\r
+\r
+\r
+I'm marking this as moreinfo since the patch as is doesn't seem to\r
+satisfy people. Personally I think the key point is that\r
+e.g. date:2012-12-10 should do something reasonable (presumably return\r
+all messages on that day, pax questions about timezone); whether we need\r
+new prefixes I'm less convinced.  However, as far as I understand it,\r
+any solution to the "single date" problem would make the "syntactic\r
+sugar prefixes" rather easy.\r
+\r
+As a meta-point, I don't think we should spend too much time and effort\r
+debating TODO; it isn't like this is some contract about deliverables,\r
+or even a document that most of us look at much.\r