--- /dev/null
+Return-Path: <markwalters1009@gmail.com>\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 F002D431E64\r
+ for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 10:11:33 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.201\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.201 tagged_above=-999 required=5\r
+ tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+ FREEMAIL_ENVFROM_END_DIGIT=1, FREEMAIL_FROM=0.001,\r
+ RCVD_IN_DNSWL_LOW=-0.7] 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 DQcyOeTQbvyk for <notmuch@notmuchmail.org>;\r
+ Wed, 29 Feb 2012 10:11:33 -0800 (PST)\r
+Received: from mail-ww0-f45.google.com (mail-ww0-f45.google.com\r
+ [74.125.82.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client\r
+ certificate requested) by olra.theworths.org (Postfix) with ESMTPS id\r
+ 50578431FD6 for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 10:11:33 -0800\r
+ (PST)\r
+Received: by wgbdt14 with SMTP id dt14so2810749wgb.2\r
+ for <notmuch@notmuchmail.org>; Wed, 29 Feb 2012 10:11:32 -0800 (PST)\r
+Received-SPF: pass (google.com: domain of markwalters1009@gmail.com designates\r
+ 10.180.80.40 as permitted sender) client-ip=10.180.80.40; \r
+Authentication-Results: mr.google.com; spf=pass (google.com: domain of\r
+ markwalters1009@gmail.com designates 10.180.80.40 as permitted\r
+ sender) smtp.mail=markwalters1009@gmail.com;\r
+ dkim=pass header.i=markwalters1009@gmail.com\r
+Received: from mr.google.com ([10.180.80.40])\r
+ by 10.180.80.40 with SMTP id o8mr3149390wix.10.1330539092203 (num_hops\r
+ = 1); Wed, 29 Feb 2012 10:11:32 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;\r
+ h=from:to:cc:subject:date:message-id:x-mailer;\r
+ bh=w+zgK/+VlrzOnfSXHwtR9P9iF+owmMb9bGmKPl8Ekzk=;\r
+ b=iNhKY8qaEPuYrwCkZASA/t9vhkL6xGn2mVbUE23rLHYGJEuwexdkHIj9MQBHTKDRof\r
+ ndp8+QgvFK3pf7OUhGYJgHUdX78vIPplBQhbE0+NOfx21hz5Eyx4mcgz34cf0kJwcP73\r
+ wK4cyBL2rVa00guiI3wCWPshdYhZurFehDGBE=\r
+Received: by 10.180.80.40 with SMTP id o8mr2525790wix.10.1330539092165;\r
+ Wed, 29 Feb 2012 10:11:32 -0800 (PST)\r
+Received: from localhost (94-192-233-223.zone6.bethere.co.uk.\r
+ [94.192.233.223]) by mx.google.com with ESMTPS id\r
+ fq10sm12015031wib.11.2012.02.29.10.11.30 (version=TLSv1/SSLv3 cipher=OTHER);\r
+ Wed, 29 Feb 2012 10:11:31 -0800 (PST)\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: [PATCH 0/5] Disable search.exclude_tags for 0.12 \r
+Date: Wed, 29 Feb 2012 18:13:04 +0000\r
+Message-Id: <1330539189-16593-1-git-send-email-markwalters1009@gmail.com>\r
+X-Mailer: git-send-email 1.7.2.3\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: Wed, 29 Feb 2012 18:11:34 -0000\r
+\r
+As requested by David (Bremner) on irc here is a patch series\r
+disabling the search.exclude_tags feature as a temporary measure for\r
+the 0.12 release.\r
+\r
+There are two options:\r
+\r
+The first is to disable the addition of the new search.exclude_tags\r
+item to the config file and stop setup from asking for it.\r
+\r
+The second is to do the above and also disable the functionality in\r
+notmuch-search.c and notmuch-count.c.\r
+\r
+The idea is that this these are minimal (and thus relatively safe)\r
+changes to make. With the first option users who have configured the\r
+functionality for themselves (while using git) will still get the\r
+feature: it just won't be pushed on users. With the second option the\r
+festure will be completely disabled.\r
+\r
+Essentially patch 1 implements the first option and patch 4 the second\r
+option. The other patches in the series update the NEWS file, the man\r
+page and the tests. If going for the first option then I would suggest\r
+applying (in addition to patch 1) patch 2 (NEWS) and probably patch 3\r
+(man) although as the functionality remains the latter is not strictly\r
+necessary. The test patch (patch 5) is not necessary as the tests set\r
+search.exclude_tags directly.\r
+\r
+If going for the second option then all the patches are needed.\r
+\r
+Finally, please could someone familiar with the config/setup code\r
+check patch 1 carefully. I have never looked at that code before and\r
+could easily have done something stupid.\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+Mark Walters (5):\r
+ config: disable addition of exclude tags for 0.12\r
+ NEWS: revert NEWS item for exclude tags for 0.12\r
+ man: remove search.exclude_tags from notmuch-config.1 for 0.12\r
+ cli: temporarily remove exclude tag support for 0.12\r
+ test: mark exclude tests broken for 0.12\r
+\r
+ NEWS | 18 ------------------\r
+ man/man1/notmuch-config.1 | 8 --------\r
+ notmuch-config.c | 3 +--\r
+ notmuch-count.c | 8 +-------\r
+ notmuch-search.c | 8 +-------\r
+ notmuch-setup.c | 19 +------------------\r
+ test/search | 2 ++\r
+ 7 files changed, 6 insertions(+), 60 deletions(-)\r
+\r
+-- \r
+1.7.2.3\r
+\r
projects / notmuch-archives.git / commitdiff