Re: Log of tagging actions

diff --git a/fe/60b346b7dbdca626a0bef68624487a516cec05 b/fe/60b346b7dbdca626a0bef68624487a516cec05
new file mode 100644 (file)
index 0000000..6b126e6
--- /dev/null
+++ b/fe/60b346b7dbdca626a0bef68624487a516cec05
@@ -0,0 +1,91 @@
+Return-Path: <sebastian.fischmeister@uwaterloo.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 104BF431FBD\r
+       for <notmuch@notmuchmail.org>; Mon, 12 May 2014 16:24:31 -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 2zhLJOCa-aWp for <notmuch@notmuchmail.org>;\r
+       Mon, 12 May 2014 16:24:27 -0700 (PDT)\r
+Received: from mailchk-m06.uwaterloo.ca (mailservices.uwaterloo.ca\r
+       [129.97.128.141])\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 263E0431FAF\r
+       for <notmuch@notmuchmail.org>; Mon, 12 May 2014 16:24:27 -0700 (PDT)\r
+Received: from connect.uwaterloo.ca (connhub2.connect.uwaterloo.ca\r
+       [129.97.149.119])\r
+       by mailchk-m06.uwaterloo.ca (8.14.4/8.14.4) with ESMTP id\r
+       s4CNO9V9018263\r
+       (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK);\r
+       Mon, 12 May 2014 19:24:10 -0400\r
+Received: from uwaterloo.ca (23.91.170.250) by connhub2.connect.uwaterloo.ca\r
+       (129.97.149.119) with Microsoft SMTP Server (TLS) id 14.3.181.6;\r
+       Mon, 12 May 2014 19:24:09 -0400\r
+From: Sebastian Fischmeister <sfischme@uwaterloo.ca>\r
+To: Tomi Ollila <tomi.ollila@iki.fi>, Istvan Marko <notmuch@kismala.com>,\r
+       <notmuch@notmuchmail.org>\r
+Subject: Re: Log of tagging actions\r
+In-Reply-To: <m2ppjnw9xr.fsf@guru.guru-group.fi>\r
+References: <871tw5n0ml.fsf@uwaterloo.ca> <m3fvkj1j88.fsf@zsu.kismala.com>\r
+       <m2ppjnw9xr.fsf@guru.guru-group.fi>\r
+User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1\r
+       (x86_64-unknown-linux-gnu)\r
+X-Homepage: http://esg.uwaterloo.ca\r
+Date: Mon, 12 May 2014 19:22:38 -0400\r
+Message-ID: <871tvy4m69.fsf@uwaterloo.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-UUID: 6c784e04-ee24-4b8d-8db7-c3cb74c114f8\r
+X-Miltered: at mailchk-m06 with ID 53715819.001 by Joe's j-chkmail\r
+       (http://j-chkmail.ensmp.fr)!\r
+X-Virus-Scanned: clamav-milter 0.98.1 at mailchk-m06\r
+X-Virus-Status: Clean\r
+X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3\r
+       (mailchk-m06.uwaterloo.ca [129.97.128.141]);\r
+       Mon, 12 May 2014 19:24:11 -0400 (EDT)\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+Reply-To: sfischme@uwaterloo.ca\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, 12 May 2014 23:24:31 -0000\r
+\r
+> I use a C wrapper to do the same (with date prefixes like 2014-05-09\r
+> (Fri) 12:47:19) -- I originally did it to do argument conversions\r
+> around .. to have date-based searches before those came to notmuch\r
+> (and I am still using it, as I don't have to type date: prefix)\r
+\r
+Having a wrapper script possible, however, it is quite a hack and\r
+doesn't potentially collect everything. There's already a\r
+.notmuch-config file, so adding a logging directive should be\r
+straightforward. It's more about whether something like this becomes\r
+part of notmuch directly.\r
+\r
+>> Would be nice to be able to log all operations done via libnotmuch\r
+>> too though.\r
+>\r
+> IIRC someone suggested/asked whether we'd get logs where all\r
+> Message-ID:s affected were logged. That could be useful (and produce\r
+> lot of log when one does notmuch tag +foobar '*')\r
+\r
+I'm not worried about the size of the logfiles. Drives are large and\r
+many utilities exist to create a rolling removal and compression of log\r
+files.\r
+\r
+  Sebastian\r