From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 42251C04A6B for ; Wed, 8 May 2019 21:26:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0570820850 for ; Wed, 8 May 2019 21:26:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=pobox.com header.i=@pobox.com header.b="QZLLuIX2"; dkim=fail reason="key not found in DNS" (0-bit key) header.d=lohutok.net header.i=@lohutok.net header.b="krD9g0tO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727608AbfEHV0E (ORCPT ); Wed, 8 May 2019 17:26:04 -0400 Received: from pb-smtp1.pobox.com ([64.147.108.70]:56883 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726591AbfEHV0E (ORCPT ); Wed, 8 May 2019 17:26:04 -0400 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id EF2121558D0; Wed, 8 May 2019 17:26:01 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject:to:cc :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=6SEfQYzoAA5A z1r8jXJh7Fu8zMk=; b=QZLLuIX2yE6OfWWbdXZs6he2J0D1TxzorxJglvFrvwP5 UndjacVmw3wFT0qdNn8WBRDEK4mbZPg5c2tIds+eMc44cXzksnitfwZ5Sn+nIOZF 6R6EXponUrtH+u+0xI7Se12D6s21vXZ1ijvuwiA7dxireFhILXj73By3FGBf140= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id A4BBA1558CF; Wed, 8 May 2019 17:26:01 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lohutok.net; h=subject:to:cc:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=2018-11.pbsmtp; bh=mDW8bd+txKyONY0k/tzVtWxCEtOq0FB31ZdkygB5Xwc=; b=krD9g0tOgdG8Es2pzdLMA2uZBWeK2cF2ZyEHMV6CBtIhplfqBJStqtB6AyLNI1GRdkRVSn+uDUfCfMB+a4CFN6WKcqfO+Wm/sZwpEi6+W88Gho7NKBqCdfchYmL1IGE0YY1QLsd+UhuBHcPUflgRXJp4arQ8okCJ67C6AAm9YJg= Received: from [192.168.0.10] (unknown [81.101.15.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 7DE821558CE; Wed, 8 May 2019 17:26:00 -0400 (EDT) Subject: Re: [patch 0/4] SPDX: First batch of patches To: Thomas Gleixner Cc: linux-spdx@vger.kernel.org References: <20190507121952.495564307@linutronix.de> <89822409-4a13-ab4f-5389-1cbd755db227@lohutok.net> From: Allison Randal Message-ID: Date: Wed, 8 May 2019 22:25:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: E05FF306-71D7-11E9-95ED-46F8B7964D18-44123303!pb-smtp1.pobox.com Sender: linux-spdx-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-spdx@vger.kernel.org On 5/8/19 9:23 PM, Thomas Gleixner wrote: > > Yes, the scripts produce logs and of course once the patch is applied you > can see from the diffstat which files are touched. So we have lots of ways > to figure out what has been changed and its preserved in the git history > forever. Nod, but what I meant was the "wall of shame" file that the lawyers wanted, which preserved each variant license notice text and a list of the files that had it removed. I thought the idea was horrible, and said so at the time, but they aren't wrong that the GPLv2 has a requirement to "keep intact all the notices that refer to this License". None of us managed to come up with a better alternative than moving the notices into a doc file, with some introductory text to say "please never do this again, just use SPDX headers". Though, maybe it would be better if I said nothing and allowed the whole idea to be forgotten... Allison