database error
[notmuch-archives.git] / 04 / 3d9437332d0d10eef05c33eb3b60a9a8102439
1 Return-Path: <prvs=133ac4588=jrosenthal@jhu.edu>\r
2 X-Original-To: notmuch@notmuchmail.org\r
3 Delivered-To: notmuch@notmuchmail.org\r
4 Received: from localhost (localhost [127.0.0.1])\r
5         by olra.theworths.org (Postfix) with ESMTP id 3D132429E28\r
6         for <notmuch@notmuchmail.org>; Wed,  8 Jun 2011 12:18:49 -0700 (PDT)\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -2.3\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
12         tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\r
13 Received: from olra.theworths.org ([127.0.0.1])\r
14         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
15         with ESMTP id jBKLdnOXgoc9 for <notmuch@notmuchmail.org>;\r
16         Wed,  8 Jun 2011 12:18:48 -0700 (PDT)\r
17 Received: from ipex4.johnshopkins.edu (ipex4.johnshopkins.edu\r
18         [128.220.161.141]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
19         (No client certificate requested)\r
20         by olra.theworths.org (Postfix) with ESMTPS id 8C61E431FB6\r
21         for <notmuch@notmuchmail.org>; Wed,  8 Jun 2011 12:18:48 -0700 (PDT)\r
22 X-IronPort-Anti-Spam-Filtered: true\r
23 X-IronPort-Anti-Spam-Result: ApwEAODJ700KoSAO/2dsb2JhbABTpyy9aoh1hiMEkRuPZw\r
24 X-IronPort-AV: E=Sophos;i="4.65,339,1304308800"; d="scan'208";a="76243942"\r
25 Received: from watt.hwcampus.jhu.edu ([10.161.32.14])\r
26         by ipex4.johnshopkins.edu with ESMTP/TLS/ADH-AES256-SHA;\r
27         08 Jun 2011 15:18:47 -0400\r
28 Received: by watt.hwcampus.jhu.edu (Postfix, from userid 502)\r
29         id 58DDB85AD9F; Wed,  8 Jun 2011 15:18:47 -0400 (EDT)\r
30 From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
31 To: Jameson Graef Rollins <jrollins@finestructure.net>,\r
32         Carl Worth <cworth@cworth.org>, Notmuch Mail <notmuch@notmuchmail.org>\r
33 Subject: Re: tag sharing [was: Re: release-candidate/0.6 redux]\r
34 In-Reply-To: <87vcwg2p2m.fsf@servo.factory.finestructure.net>\r
35 References: <1306619520-25730-1-git-send-email-jrollins@finestructure.net>\r
36         <87hb8eebdi.fsf@servo.factory.finestructure.net>\r
37         <87pqmyn224.fsf@servo.factory.finestructure.net>\r
38         <87zklyjshd.fsf@yoom.home.cworth.org>\r
39         <87sjrng5k3.fsf@servo.factory.finestructure.net>\r
40         <87oc2bjgrs.fsf@yoom.home.cworth.org>\r
41         <8762oigc0y.fsf@servo.factory.finestructure.net>\r
42         <87boya98sf.fsf@gogo.home>\r
43         <87vcwg2p2m.fsf@servo.factory.finestructure.net>\r
44 User-Agent: Notmuch/0.5-192-gecd6549 (http://notmuchmail.org) Emacs/23.2.1\r
45         (x86_64-apple-darwin)\r
46 Date: Wed, 08 Jun 2011 15:18:47 -0400\r
47 Message-ID: <m1wrgw3ze0.fsf@watt.hwcampus.jhu.edu>\r
48 MIME-Version: 1.0\r
49 Content-Type: text/plain; charset=us-ascii\r
50 X-BeenThere: notmuch@notmuchmail.org\r
51 X-Mailman-Version: 2.1.13\r
52 Precedence: list\r
53 List-Id: "Use and development of the notmuch mail system."\r
54         <notmuch.notmuchmail.org>\r
55 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
56         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
57 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
58 List-Post: <mailto:notmuch@notmuchmail.org>\r
59 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
60 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
61         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
62 X-List-Received-Date: Wed, 08 Jun 2011 19:18:49 -0000\r
63 \r
64 On Wed, 08 Jun 2011 10:46:57 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
65 > Did you guys try to address the issue of tag removal at all?  I've been\r
66 > trying to decide if this is something we need to worry about or not.\r
67 > For instance, if cworth pushed a tag ".needs-review", you would probably\r
68 > want to have that tag removed if cworth removed it.  I guess\r
69 > alternatively he could just push the tag ".reviewed" to nullify the\r
70 > meaning of the previous one.  I'm not sure that would work in all cases,\r
71 > though.\r
72 \r
73 Yes, if he deletes the tag "public.needs-review" in his notmuch, and\r
74 then pushes it, it will delete the tag "cworth.needs-review" from yours.\r
75 \r
76 A couple points about this:\r
77 \r
78 1. If you added your own "needs-review" tag to things that have a\r
79 "cworth.needs-review" tag, that wouldn't be deleted. In other words,\r
80 cworth's actions will only affect that namespace. Now, if you delete it,\r
81 and push it, and Carl pulls back from you (meaning he trusts you), then\r
82 it would be deleted on his. When he pushes next, it will be deleted on\r
83 everyone who pulls from him.\r
84 \r
85 I'm sure there are resolution paradoxes here. It only had a ten-minute\r
86 trial run one day on IRC with me and someone else.\r
87 \r
88 2. The history is available. If you run `nm-remote history msg-id`, it\r
89 will show you its history of being added and deleted. I think it will\r
90 show by whom it was added or deleted as well, but I don't quite remember\r
91 (I hacked this up over a year ago).\r
92 \r