From: Thomas Gleixner <tglx@linutronix.de>
To: Allison Randal <allison@lohutok.net>
Cc: linux-spdx@vger.kernel.org
Subject: Re: [patch 0/4] SPDX: First batch of patches
Date: Wed, 8 May 2019 23:29:31 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1905082328350.2057@nanos.tec.linutronix.de> (raw)
In-Reply-To: <a1c6fde6-49d1-20e0-8a33-adc161833acc@lohutok.net>
On Wed, 8 May 2019, Allison Randal wrote:
> 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...
Ahhh that one. That's an easy to do add on if people insist ....
next prev parent reply other threads:[~2019-05-08 21:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 12:19 [patch 0/4] SPDX: First batch of patches Thomas Gleixner
2019-05-07 12:19 ` [patch 2/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 2 Thomas Gleixner
2019-05-07 12:19 ` [patch 3/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 3 Thomas Gleixner
2019-05-07 12:19 ` [patch 4/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 4 Thomas Gleixner
2019-05-07 13:59 ` [patch 0/4] SPDX: First batch of patches Thomas Gleixner
2019-05-07 14:03 ` [patch 1/4] treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 1 Thomas Gleixner
2019-05-07 14:17 ` [patch 0/4] SPDX: First batch of patches Greg KH
2019-05-07 14:19 ` Thomas Gleixner
2019-05-07 18:14 ` Greg KH
2019-05-07 18:43 ` Thomas Gleixner
2019-05-07 18:58 ` Greg KH
2019-05-08 6:25 ` Thomas Gleixner
2019-05-08 6:46 ` Greg KH
2019-05-08 9:26 ` Thomas Gleixner
2019-05-08 9:51 ` Greg KH
2019-05-08 10:09 ` Greg KH
2019-05-08 20:40 ` Thomas Gleixner
2019-05-08 17:29 ` Allison Randal
2019-05-08 20:23 ` Thomas Gleixner
2019-05-08 21:25 ` Allison Randal
2019-05-08 21:29 ` Thomas Gleixner [this message]
2019-05-08 21:33 ` Allison Randal
2019-05-08 21:36 ` J Lovejoy
2019-05-08 21:58 ` Thomas Gleixner
2019-05-09 4:04 ` J Lovejoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1905082328350.2057@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=allison@lohutok.net \
--cc=linux-spdx@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).