mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Kate Stewart" <kstewart@linuxfoundation.org>,
	"Nishad Kamdar" <nishadkamdar@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Use the correct style for SPDX License Identifier
Date: Mon, 27 Apr 2020 11:59:16 -0700	[thread overview]
Message-ID: <16b209d0b0c8034db62f8d4d0a260a00f0aa5d5e.camel@perches.com> (raw)
In-Reply-To: <20200427183629.GA20158@kroah.com>

On Mon, 2020-04-27 at 20:36 +0200, Greg Kroah-Hartman wrote:
> On Mon, Apr 27, 2020 at 11:01:38AM -0700, Joe Perches wrote:
> > On Mon, 2020-04-27 at 19:46 +0200, Greg Kroah-Hartman wrote:
> > > On Mon, Apr 27, 2020 at 10:41:58AM -0700, Joe Perches wrote:
> > > > On Mon, 2020-04-27 at 19:29 +0200, Greg Kroah-Hartman wrote:
[]
> > > > > I thought we were supposed to use 'GPL-2.0-or-newer' because 'GPL-2.0+'
> > > > > > is deprecated in some newer version of the SPDX standard?
> > > > > > 
> > > > > > <shrug>
> > > > > 
> > > > > The kernel follows the "older" SPDX standard, but will accept either,
> > > > > it's up to the author.  It is all documented in LICENSES/ if people
> > > > > really want to make sure.
> > > > 
> > > > I think the kernel should prefer the "newer" SPDX standard
> > > > for any/all changes to these lines.
> > > > ---
> > > >  LICENSES/preferred/GPL-2.0 | 8 ++++----
> > > >  1 file changed, 4 insertions(+), 4 deletions(-)
> > > > 
> > > > diff --git a/LICENSES/preferred/GPL-2.0 b/LICENSES/preferred/GPL-2.0
> > > > index ff0812..c50f93 100644
> > > > --- a/LICENSES/preferred/GPL-2.0
> > > > +++ b/LICENSES/preferred/GPL-2.0
> > > > @@ -8,13 +8,13 @@ Usage-Guide:
> > > >    tag/value pairs into a comment according to the placement
> > > >    guidelines in the licensing rules documentation.
> > > >    For 'GNU General Public License (GPL) version 2 only' use:
> > > > -    SPDX-License-Identifier: GPL-2.0
> > > > -  or
> > > >      SPDX-License-Identifier: GPL-2.0-only
> > > > +  or the deprecated alternative
> > > > +    SPDX-License-Identifier: GPL-2.0
> > > >    For 'GNU General Public License (GPL) version 2 or any later version' use:
> > > > -    SPDX-License-Identifier: GPL-2.0+
> > > > -  or
> > > >      SPDX-License-Identifier: GPL-2.0-or-later
> > > > +  or the deprecated alternative
> > > > +    SPDX-License-Identifier: GPL-2.0+
> > > >  License-Text:
> > > 
> > > At the moment, I do not, as the current ones are not "depreciated" at
> > > all.
> > 
> > https://spdx.org/licenses/
> > 
> > shows the GPL-2.0 and GPL-2.0+ as deprecated.
> > 
> > https://spdx.org/licenses/GPL-2.0.html
> > https://spdx.org/licenses/GPL-2.0+.html
> > 
> 
> Again, we are not using the "new" version of the SPDX specification just
> yet.  We started out using one specific version, let's get the whole
> kernel converted first before worrying about trying to keep up with
> their newer releases please.  We still have a ways to go...

It seems you refer to yourself using the majestic plural.

There's already ~80% use of SPDX-License-Identifier and the
-only versions are already about 25% of the existing uses.

There's no real reason not to prefer the latest versions
over the deprecated ones.



  reply	other threads:[~2020-04-27 18:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 13:35 Nishad Kamdar
2020-04-27  7:25 ` Christoph Hellwig
2020-05-02  8:57   ` Nishad Kamdar
2020-04-27 15:56 ` Darrick J. Wong
2020-04-27 17:29   ` Greg Kroah-Hartman
2020-04-27 17:41     ` Joe Perches
2020-04-27 17:46       ` Greg Kroah-Hartman
2020-04-27 18:01         ` Joe Perches
2020-04-27 18:36           ` Greg Kroah-Hartman
2020-04-27 18:59             ` Joe Perches [this message]
2020-04-27 19:40               ` Linus Torvalds
2020-04-27 20:38                 ` Joe Perches
2020-04-27 20:46                   ` Linus Torvalds
2020-04-29  0:20                     ` 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=16b209d0b0c8034db62f8d4d0a260a00f0aa5d5e.camel@perches.com \
    --to=joe@perches.com \
    --cc=darrick.wong@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel@pengutronix.de \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nishadkamdar@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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®