From: Joe Perches <joe@perches.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
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 13:22:54 -0700 [thread overview]
Message-ID: <dac95ea92cf3334318cf95d133553c8b7d1110b5.camel@perches.com> (raw)
In-Reply-To: <20180822201201.GC19458@bombadil.infradead.org>
On Wed, 2018-08-22 at 13:12 -0700, Matthew Wilcox wrote:
> On Wed, Aug 22, 2018 at 12:47:57PM -0700, Joe Perches wrote:
> > Perhaps it's better to stick to a single SPDX version style for
> > all kernel files.
> >
> > Right now, there are already several -only and -or-later uses.
> >
> > $ git grep -P 'SPDX-License-Identifier.*(?:-or-later|-only)'| wc -l
> > 144
> >
> > So perhaps a patch and a tool to do the reverse conversion:
>
> No. Any tool which does anything useful just has to understand both
> 2.0 and 3.0 naming. They're aliases for each other, that's all.
But that same tool would have to be updated if ever
yet-another spdx version appears.
So it'd probably be better to support just 1 version.
prev parent reply other threads:[~2018-08-22 20:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 15:45 [PATCH V2] license-rules.rst and LICENSES: Use only spdx version 3 with -only and -or-later Joe Perches
2018-08-22 18:01 ` Joe Perches
2018-08-22 18:13 ` Linus Torvalds
2018-08-22 19:17 ` Thomas Gleixner
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 [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=dac95ea92cf3334318cf95d133553c8b7d1110b5.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@linux-foundation.org \
--cc=willy@infradead.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).