linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Joe Perches <joe@perches.com>
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 05:37:11 -0600	[thread overview]
Message-ID: <20180817053711.1f7ef05b@lwn.net> (raw)
In-Reply-To: <f9a4cd2b1c1cd7938a4e0b8aa9489a0ad96669ca.1534443693.git.joe@perches.com>

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.

If we *do* keep it for some reason, it needs a comment saying what it
does and why it exists.

Thanks,

jon

  parent reply	other threads:[~2018-08-17 11:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 18:26 [PATCH] license-rules.rst and LICENSES: Use only spdx version 3 with -only and -or-later Joe Perches
2018-08-17  6:52 ` Christoph Hellwig
2018-08-17 11:37 ` Jonathan Corbet [this message]
2018-08-17 16:02   ` Joe Perches

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=20180817053711.1f7ef05b@lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linuxfoundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=joe@perches.com \
    --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;
as well as URLs for NNTP newsgroup(s).