Re: [PATCH] Add configurable changed tag to messages that have been changed on disk

diff --git a/23/c2b7008f4d7b408dcf59180c4f437719e4b57a b/23/c2b7008f4d7b408dcf59180c4f437719e4b57a
new file mode 100644 (file)
index 0000000..205b377
--- /dev/null
+++ b/23/c2b7008f4d7b408dcf59180c4f437719e4b57a
@@ -0,0 +1,80 @@
+Return-Path: <david@tethera.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 C4D9F431FBD\r
+       for <notmuch@notmuchmail.org>; Sat, 12 Apr 2014 08:58:42 -0700 (PDT)\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 qa1KrGASEnv4 for <notmuch@notmuchmail.org>;\r
+       Sat, 12 Apr 2014 08:58:38 -0700 (PDT)\r
+Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155])\r
+       (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id BCE06431FBC\r
+       for <notmuch@notmuchmail.org>; Sat, 12 Apr 2014 08:58:38 -0700 (PDT)\r
+Received: from remotemail by yantan.tethera.net with local (Exim 4.80)\r
+       (envelope-from <david@tethera.net>)\r
+       id 1WZ0K9-00048N-4R; Sat, 12 Apr 2014 12:58:33 -0300\r
+Received: (nullmailer pid 1288 invoked by uid 1000); Sat, 12 Apr 2014\r
+       15:58:29 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: David Mazieres expires 2014-07-10 PDT\r
+       <mazieres-7je64uqare55j4eig77r2axtva@temporary-address.scs.stanford.edu>,\r
+       Gaute Hope <eg@gaute.vetsj.com>\r
+Subject: Re: [PATCH] Add configurable changed tag to messages that have been\r
+       changed on disk\r
+In-Reply-To: <877g6v3lb9.fsf@ta.scs.stanford.edu>\r
+References: <1396800683-9164-1-git-send-email-eg@gaute.vetsj.com>\r
+       <87wqf2gqig.fsf@ta.scs.stanford.edu> <1397140962-sup-6514@qwerzila>\r
+       <87wqexnqvb.fsf@ta.scs.stanford.edu> <87k3aw5dj5.fsf@zancas.localnet>\r
+       <877g6v3lb9.fsf@ta.scs.stanford.edu>\r
+User-Agent: Notmuch/0.17+180~g8977b1a (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sat, 12 Apr 2014 12:58:29 -0300\r
+Message-ID: <87mwfq4k0q.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: notmuch <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: Sat, 12 Apr 2014 15:58:42 -0000\r
+\r
+dm-list-email-notmuch@scs.stanford.edu writes:\r
+\r
+>\r
+> As far as updating the test suite, etc., it's almost certain that the\r
+> core notmuch developers would be unsatisfied with whatever I've done,\r
+> since the code base is very clean and has a very uniform style.  So when\r
+> I say I'd want some "indication that such a change could be upstreamed,"\r
+> I mean more specifically that someone would be willing to shepherd the\r
+> process of getting the code into shape.\r
+>\r
+\r
+I think it depends on your definition of shepherd. If it means review\r
+your patches and tell you what needs to be done, then we can probably\r
+handle that. Things tend to stall if the patch proposer loses interest\r
+after the first review, so we're pretty far from "fire and forget".\r
+\r
+I'd like to hear one or two more opinions from regular contributors\r
+before I say "yes, this is something we want to do."\r
+\r
+cheers,\r
+\r
+d\r