Re: Replacing my name/email with "me" (or similar) in author lists

diff --git a/32/632fb7edb72857716bde2f53145bee7b76254f b/32/632fb7edb72857716bde2f53145bee7b76254f
new file mode 100644 (file)
index 0000000..4048ab3
--- /dev/null
+++ b/32/632fb7edb72857716bde2f53145bee7b76254f
@@ -0,0 +1,76 @@
+Return-Path: <prvs=400325a14=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 27776431FAE\r
+       for <notmuch@notmuchmail.org>; Thu,  1 Mar 2012 06:27:53 -0800 (PST)\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 bZd3ewdZVn3k for <notmuch@notmuchmail.org>;\r
+       Thu,  1 Mar 2012 06:27:52 -0800 (PST)\r
+Received: from ipex1.johnshopkins.edu (ipex1.johnshopkins.edu [162.129.8.141])\r
+       (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 926D1431E82\r
+       for <notmuch@notmuchmail.org>; Thu,  1 Mar 2012 06:27:52 -0800 (PST)\r
+X-IronPort-AV: E=Sophos;i="4.73,511,1325480400"; d="scan'208";a="132819346"\r
+Received: from unknown (HELO watt) ([10.161.33.18])\r
+       by ipex1.johnshopkins.edu with ESMTP/TLS/AES256-SHA;\r
+       01 Mar 2012 09:27:51 -0500\r
+Received: from jkr by watt with local (Exim 4.76)\r
+       (envelope-from <jrosenthal@jhu.edu>)\r
+       id 1S36zT-0001tW-VP; Thu, 01 Mar 2012 09:28:20 -0500\r
+From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
+To: Austin Clements <amdragon@MIT.EDU>\r
+Subject: Re: Replacing my name/email with "me" (or similar) in author lists\r
+In-Reply-To: <87k435ntnx.fsf@awakening.csail.mit.edu>\r
+References: <slrnjki3c7.tcm.quite@kelebek.lublin.se>\r
+       <20120226112210.5422.8471@brick.lan>\r
+       <87ehthfsyn.fsf@schoepe.localhost> <87fwdxk062.fsf@zancas.localnet>\r
+       <87ehth8dd2.fsf@hermes.hocat.ca> <878vjl3ck3.fsf@jhu.edu>\r
+       <20120229153657.GA772@mit.edu> <877gz5tz8p.fsf@jhu.edu>\r
+       <87k435ntnx.fsf@awakening.csail.mit.edu>\r
+User-Agent: Notmuch/0.11.1+263~g4fa77d0 (http://notmuchmail.org)\r
+       Emacs/24.0.93.1 (i686-pc-linux-gnu)\r
+Date: Thu, 01 Mar 2012 09:28:19 -0500\r
+Message-ID: <87y5rkxunw.fsf@jhu.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+Cc: Notmuch Mail <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: Thu, 01 Mar 2012 14:27:53 -0000\r
+\r
+On Wed, 29 Feb 2012 17:47:46 -0500, Austin Clements <amdragon@MIT.EDU> wrote:\r
+> > On Wed, 29 Feb 2012 10:36:57 -0500, Austin Clements <amdragon@MIT.EDU> wrote:\r
+> > > What if the output of search (say, specifically the JSON format)\r
+> > > included information on each message in the thread such as the\r
+> > > 'message' production from devel/schemata minus the body field?  \r
+> [...]\r
+> I was suggesting just using notmuch_thread_get_toplevel_messages in\r
+> search (essentially, mixing a bit of show into search).  No library\r
+> changes necessary.\r
+\r
+In any event, I'd really love to see something like this. Because I work\r
+remotely, over an ssh tunnel, and it's nice to have various scripts\r
+local. However, things like notmuch_addresses and my recipient_search\r
+script have to run on the server, since they need bindings-level access\r
+to the database. If I could get the JSON you describe over the wire, I\r
+could probably just make one remote call and then confine my local work\r
+to JSON parsing. A niche need, I realize.\r