Weird behaviour in notmuch new

diff --git a/65/a316875b0e1de44de4110f6386fbef191c8a56 b/65/a316875b0e1de44de4110f6386fbef191c8a56
new file mode 100644 (file)
index 0000000..86cc724
--- /dev/null
+++ b/65/a316875b0e1de44de4110f6386fbef191c8a56
@@ -0,0 +1,97 @@
+Return-Path: <m.walters@qmul.ac.uk>\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 00266431FCF\r
+       for <notmuch@notmuchmail.org>; Sat, 22 Feb 2014 17:08:20 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+       tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+       NML_ADSP_CUSTOM_MED=1.2, 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 982dqIjLjbDg for <notmuch@notmuchmail.org>;\r
+       Sat, 22 Feb 2014 17:08:15 -0800 (PST)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\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 F1E77431FBF\r
+       for <notmuch@notmuchmail.org>; Sat, 22 Feb 2014 17:08:14 -0800 (PST)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+       by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+       (envelope-from <m.walters@qmul.ac.uk>)\r
+       id 1WHNYC-0005rC-8V; Sun, 23 Feb 2014 01:08:12 +0000\r
+Received: from 93-97-24-31.zone5.bethere.co.uk ([93.97.24.31] helo=localhost)\r
+       by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)\r
+       (envelope-from <m.walters@qmul.ac.uk>)\r
+       id 1WHNYC-000123-15; Sun, 23 Feb 2014 01:08:12 +0000\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: Weird behaviour in notmuch new\r
+User-Agent: Notmuch/0.15.2+484~gfb59956 (http://notmuchmail.org) Emacs/23.4.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sun, 23 Feb 2014 01:08:10 +0000\r
+Message-ID: <87siray6th.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 93.97.24.31\r
+X-QM-Geographic: According to ripencc,\r
+       this message was delivered by a machine in Britain (UK) (GB).\r
+X-QM-SPAM-Info: Sender has good ham record.  :)\r
+X-QM-Body-MD5: e31def657201e6b3eb79ed52beb6d56b (of first 20000 bytes)\r
+X-SpamAssassin-Score: 0.0\r
+X-SpamAssassin-SpamBar: /\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+       determine if it is\r
+       spam. We require at least 5.0 points to mark a message as spam.\r
+       This message scored 0.0 points. Summary of the scoring: \r
+       * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+       provider *      (markwalters1009[at]gmail.com)\r
+       *  0.0 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\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: Sun, 23 Feb 2014 01:08:21 -0000\r
+\r
+\r
+Hi\r
+\r
+I was experimenting with letting notmuch new take an argument to tell it\r
+to scan only a particular directory (and sub-directories) for new\r
+messages. I came across the following strange behaviour which is also\r
+present in master (with a fresh database)\r
+\r
+I have a bunch of maildirs in /home/mail: so folders .mail.foo/\r
+.mail.bar/ each of which has cur/new/tmp and all the messages are in\r
+cur.\r
+\r
+If I do mv .mail.foo .mail.bar/ and run notmuch new I get the expected\r
+lots of renames (900 or so in the case I was trying). But if I then do\r
+mv .mail.bar/.mail.foo . and run notmuch new almost all the messages get\r
+removed (but 30 renames do get detected). If I then do touch .mail.foo/*\r
+the messages get found again\r
+\r
+I am guessing the 30 renames might be because those 30 have duplicates\r
+somewhere else. \r
+\r
+But the other behaviour has me puzzled.\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
+\r