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 22:23:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1905082222320.2057@nanos.tec.linutronix.de> (raw)
In-Reply-To: <89822409-4a13-ab4f-5389-1cbd755db227@lohutok.net>
Allison,
On Wed, 8 May 2019, Allison Randal wrote:
> On 5/7/19 1:19 PM, Thomas Gleixner wrote:
> > Hi!
> >
> > As promised here are the first 4 automatically generated patches. Each
> > patch handles exactly one match pattern (rule).
>
> These look great, Thomas, thanks!
>
> Are you automatically logging which files were modified by each pattern
> match, for the legally conservative hack we talked about, preserving a
> historical record of altered license notices in a doc file?
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.
Thanks,
tglx
next prev parent reply other threads:[~2019-05-08 20:23 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 [this message]
2019-05-08 21:25 ` Allison Randal
2019-05-08 21:29 ` Thomas Gleixner
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.1905082222320.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).