mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	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>,
	Jonathan Corbet <corbet@lwn.net>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH V2] license-rules.rst and LICENSES: Use only spdx version 3 with -only and -or-later
Date: Wed, 22 Aug 2018 21:17:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1808222115050.1652@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CA+55aFyd5D9Rj2Wm+rP9QnZg2Jd_LKqPTKTmPv+doYN=JXra=w@mail.gmail.com>

On Wed, 22 Aug 2018, Linus Torvalds wrote:
> On Wed, Aug 22, 2018 at 11:01 AM Joe Perches <joe@perches.com> wrote:
> >
> > How likely is it that this is applied at rc1?
> 
> I'm staying out of the crazy license name bikeshedding, so it's going
> to be up to the people who have decided they care.
> 
> I think whoever *did* care and argued for the change to the SPDX
> format is a hopeless wanker. "GPL-2.0{-only,-or-later}" is in no ways
> better than the "GPL-2.0{,+}" that was in an earlier version of the
> SPDX spec
> 
> So I want nothing at all to do with pointless patches. Life is too
> short to deal with this.
> 
> Other people disagree, so I expect I will get these kinds of stupid
> noise patches through the usual channels.

I'm not a great fan of that change either. We have settled on a well
documented and machine readable format. External tools have to be able to
deal with SPDX versions anyway and if we do this now, then we have the next
round of pointless churn in a year when the SPDX folks decide to rename yet
another license identifier which is used in the kernel.

Thanks,

	tglx

  reply	other threads:[~2018-08-22 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 15:45 Joe Perches
2018-08-22 18:01 ` Joe Perches
2018-08-22 18:13   ` Linus Torvalds
2018-08-22 19:17     ` Thomas Gleixner [this message]
2018-08-22 19:46       ` Greg Kroah-Hartman
2018-08-22 19:47       ` Joe Perches
2018-08-22 20:12         ` Matthew Wilcox
2018-08-22 20:22           ` 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=alpine.DEB.2.21.1808222115050.1652@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --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=torvalds@linux-foundation.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®