From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
Rob Herring <rob.herring@linaro.org>,
Jonas Oberg <jonas@fsfe.org>,
Andrew Morton <akpm@linuxfoundation.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] license-rules.rst and LICENSES: Use only spdx version 3 with -only and -or-later
Date: Fri, 17 Aug 2018 09:02:15 -0700 [thread overview]
Message-ID: <960e6632bb6c9e45845e9078af6dd5939cd3bea6.camel@perches.com> (raw)
In-Reply-To: <20180817053711.1f7ef05b@lwn.net>
On Fri, 2018-08-17 at 05:37 -0600, Jonathan Corbet wrote:
> On Thu, 16 Aug 2018 11:26:03 -0700
> Joe Perches <joe@perches.com> wrote:
>
> > The current linux-kernel source git tree has a mixture of the deprecated
> > spdx version 2 and the newer version 3 uses.
> >
> > Update the process/license-rules.rst file to show only the version 3 style
> > and use only the version 3 styles in LICENSES.
> >
> > Add a script to update all old versions in the tree as well.
> >
> > I suggest this be applied and the script be run and applied immediately
> > after an -rc1. The script could also be used at any time after the initial
> > use to update any other deprecated spdx license uses.
>
> All seems OK to me, with one question: if we're going to run the script
> and fix everything up, do we really need to add that script to the tree
> as well? It seems like something we shouldn't need again.
linux-next has other files with licenses that would need to be
updated even after an -rc1
prev parent reply other threads:[~2018-08-17 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 18:26 Joe Perches
2018-08-17 6:52 ` Christoph Hellwig
2018-08-17 11:37 ` Jonathan Corbet
2018-08-17 16:02 ` Joe Perches [this message]
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=960e6632bb6c9e45845e9078af6dd5939cd3bea6.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jonas@fsfe.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rob.herring@linaro.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linuxfoundation.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
all inboxes | Powered by JetHome®