Re: tag sharing [was: Re: release-candidate/0.6 redux]

diff --git a/bc/2b0f9be0449913ec0104082e949fff4b449cf3 b/bc/2b0f9be0449913ec0104082e949fff4b449cf3
new file mode 100644 (file)
index 0000000..3ac5b6d
--- /dev/null
+++ b/bc/2b0f9be0449913ec0104082e949fff4b449cf3
@@ -0,0 +1,103 @@
+Return-Path: <prvs=131304623=jrosenthal@jhu.edu>\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 44C1A429E28\r
+       for <notmuch@notmuchmail.org>; Mon,  6 Jun 2011 10:20:04 -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 xWR9z06krArp for <notmuch@notmuchmail.org>;\r
+       Mon,  6 Jun 2011 10:20:02 -0700 (PDT)\r
+Received: from ipex4.johnshopkins.edu (ipex4.johnshopkins.edu\r
+       [128.220.161.141]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 11433431FB6\r
+       for <notmuch@notmuchmail.org>; Mon,  6 Jun 2011 10:20:02 -0700 (PDT)\r
+X-IronPort-AV: E=Sophos;i="4.65,327,1304308800"; d="scan'208";a="75620948"\r
+Received: from dyn-209-2-216-143.dyn.columbia.edu (HELO gogo.home)\r
+       ([209.2.216.143])\r
+       by ipex4.johnshopkins.edu with ESMTP/TLS/AES256-SHA;\r
+       06 Jun 2011 13:20:01 -0400\r
+Received: from jkr by gogo.home with local (Exim 4.76)\r
+       (envelope-from <jrosenthal@jhu.edu>)\r
+       id 1QTdT6-000757-UW; Mon, 06 Jun 2011 13:20:00 -0400\r
+From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>,\r
+       Carl Worth <cworth@cworth.org>, Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: Re: tag sharing [was: Re: release-candidate/0.6 redux]\r
+In-Reply-To: <8762oigc0y.fsf@servo.factory.finestructure.net>\r
+References: <1306619520-25730-1-git-send-email-jrollins@finestructure.net>\r
+       <87hb8eebdi.fsf@servo.factory.finestructure.net>\r
+       <87pqmyn224.fsf@servo.factory.finestructure.net>\r
+       <87zklyjshd.fsf@yoom.home.cworth.org>\r
+       <87sjrng5k3.fsf@servo.factory.finestructure.net>\r
+       <87oc2bjgrs.fsf@yoom.home.cworth.org>\r
+       <8762oigc0y.fsf@servo.factory.finestructure.net>\r
+User-Agent: Notmuch/0.5-192-gecd6549 (http://notmuchmail.org) Emacs/23.3.1\r
+       (i486-pc-linux-gnu)\r
+Date: Mon, 06 Jun 2011 13:20:00 -0400\r
+Message-ID: <87boya98sf.fsf@gogo.home>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\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: Mon, 06 Jun 2011 17:20:04 -0000\r
+\r
+\r
+On Mon, 06 Jun 2011 09:28:13 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
+> I've been thinking about this more and it really seems we need a way to\r
+> just share tags.  What if we had a way to export all the tags for a set\r
+> of messages as a notmuch dump file, that could just be piped into\r
+> notmuch to modify tags?  This would be a great way for lots of people to\r
+> keep tags synced on a set of messages.\r
+\r
+After a conversation with David last year about bug-tracking, I worked\r
+up a rough python-based prototype of this. It worked in terms of\r
+namespaces, so Carl could associate the namespace "public" with a list\r
+of tags he publishes to a http-accessable location. And you could\r
+associate the namespace "cworth" with those same tags.\r
+\r
+He types `whatevercommand push public` and all tags "public.*" go to an\r
+config-associated URL.\r
+\r
+You type `whatevercommand pull cworth` and the tags come down from that\r
+URL as "cworth.*".\r
+\r
+So what he has as "public.to-push" comes down to your notmuch as\r
+"cworth.to-push".\r
+\r
+It's available here:\r
+\r
+    http://commonmeasure.org/~jkr/git/nm-remote.git\r
+\r
+See these emails for more (but note that the repo url has changed to the\r
+above).\r
+    \r
+    id:"m1k4rkkchy.fsf@watt.gilman.jhu.edu"        \r
+    id:"m1hbmokbxj.fsf@watt.gilman.jhu.edu"\r
+\r
+There were some details and inherent ambiguities about conflict\r
+resolution, and the above emails explain how I dealt with them. \r
+\r
+Note also that it uses python's configparser, which will overwrite your\r
+config -- which means it'll get rid of your comments. So if you use any\r
+of the config-writing commands, make sure you back up your config first.\r
+\r
+Best,\r
+Jesse\r