Re: [PATCH 1/2] Add Google Inc. to AUTHORS as a contributor.

diff --git a/ae/005bc173bd44f3105b7dace546d3e1ff771757 b/ae/005bc173bd44f3105b7dace546d3e1ff771757
new file mode 100644 (file)
index 0000000..69dc30b
--- /dev/null
+++ b/ae/005bc173bd44f3105b7dace546d3e1ff771757
@@ -0,0 +1,80 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id CF2FF6DE00E6\r
+ for <notmuch@notmuchmail.org>; Mon,  1 Aug 2016 21:51:28 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.011\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[AWL=0.000,\r
+  SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 1cJfQN0nyLra for <notmuch@notmuchmail.org>;\r
+ Mon,  1 Aug 2016 21:51:19 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id D966B6DE00B8\r
+ for <notmuch@notmuchmail.org>; Mon,  1 Aug 2016 21:51:18 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1bURfw-0000JS-OH; Tue, 02 Aug 2016 00:51:32 -0400\r
+Received: (nullmailer pid 23503 invoked by uid 1000);\r
+ Tue, 02 Aug 2016 04:51:11 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Matt Armstrong <marmstrong@google.com>, notmuch@notmuchmail.org\r
+Subject: Re: [PATCH 1/2] Add Google Inc. to AUTHORS as a contributor.\r
+In-Reply-To: <qf5twf4mqza.fsf@marmstrong-linux.kir.corp.google.com>\r
+References: <1469136633-19235-1-git-send-email-marmstrong@google.com>\r
+ <1469136633-19235-2-git-send-email-marmstrong@google.com>\r
+ <877fcdltd7.fsf@zancas.localnet>\r
+ <qf5twf4mqza.fsf@marmstrong-linux.kir.corp.google.com>\r
+User-Agent: Notmuch/0.22.1+61~g2ce0f13 (https://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Tue, 02 Aug 2016 13:51:11 +0900\r
+Message-ID: <87wpjzvkn4.fsf@maritornes.cs.unb.ca>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 02 Aug 2016 04:51:28 -0000\r
+\r
+Matt Armstrong <marmstrong@google.com> writes:\r
+>\r
+> Thanks for thinking about this David.\r
+>\r
+> The good news: in looking into this further, the issue of leaving (c)\r
+> claims in code is secondary.  The primary thing I'm supposed to do is\r
+> send patches with my work email.\r
+>\r
+> If I become a significant author in some file, adding a (c) Google makes\r
+> sense if that the normal thing to do in notmuch.  I'll keep that in\r
+> mind.\r
+\r
+Yeah, for example most people creating a new file will put their name in\r
+the copyright header. Or maybe rewriting a significant amount.\r
+But it's an individual judgement call.\r
+\r
+>\r
+> Google's open source lawyers tell me that regardless of what (c) marks\r
+> appear in code, the author of code (e.g. significant patches) retains\r
+> copyright unless other arrangements are made, such as those you see in\r
+> FSF projects (https://www.gnu.org/licenses/why-assign.en.html).\r
+\r
+Never argue with a happy lawyer, that's motto :). It sounds like we're\r
+good to go; I merged patch 2/2 after moving the NEWS. Then I wanted to\r
+shorten the summary line of the commit, which got a bit more intrusive\r
+than I wanted, hopefully it conveys the intent of the existing message.\r
+\r
+d\r