From: Thomas Gleixner <tglx@linutronix.de>
To: Luis Chamberlain <mcgrof@kernel.org>,
tj@kernel.org, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, jeyu@kernel.org, shuah@kernel.org
Cc: bvanassche@acm.org, dan.j.williams@intel.com, joe@perches.com,
mcgrof@kernel.org, keescook@chromium.org, rostedt@goodmis.org,
minchan@kernel.org, linux-spdx@vger.kernel.org,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Goldwyn Rodrigues <rgoldwyn@suse.com>, Kuno Woudt <kuno@frob.nl>,
Richard Fontana <fontana@sharpeleven.org>,
copyleft-next@lists.fedorahosted.org,
Ciaran Farrell <Ciaran.Farrell@suse.com>,
Christopher De Nicolo <Christopher.DeNicolo@suse.com>,
Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [PATCH v9 1/6] LICENSES: Add the copyleft-next-0.3.1 license
Date: Mon, 23 May 2022 23:10:37 +0200 [thread overview]
Message-ID: <87h75g0xbm.ffs@tglx> (raw)
In-Reply-To: <20211029184500.2821444-2-mcgrof@kernel.org>
On Fri, Oct 29 2021 at 11:44, Luis Chamberlain wrote:
> preferred. A summary of benefits why projects outside of Linux might
> prefer to use copyleft-next >= 0.3.1 over GPLv2:
>
<snip>
>
> o copyleft-next has a 'built-in or-later' provision
Not convinced that this is a benefit under all circumstances, but that's
a philosopical problem. The real problem is this:
> +Valid-License-Identifier: copyleft-next-0.3.1
and
> +11. Later License Versions
> +
> + The Copyleft-Next Project may release new versions of copyleft-next,
> + designated by a distinguishing version number ("Later Versions").
> + Unless I explicitly remove the option of Distributing Covered Works
> + under Later Versions, You may Distribute Covered Works under any Later
> + Version.
If I want to remove this option, then how do I express this with a SPDX
license identifier?
Sigh!
tglx
next prev parent reply other threads:[~2022-05-23 21:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 18:44 [PATCH v9 0/6] test_sysfs: add new selftest for sysfs Luis Chamberlain
2021-10-29 18:44 ` [PATCH v9 1/6] LICENSES: Add the copyleft-next-0.3.1 license Luis Chamberlain
2022-05-23 21:10 ` Thomas Gleixner [this message]
2022-05-24 13:59 ` Richard Fontana
2022-05-25 17:10 ` Luis Chamberlain
2022-05-25 19:13 ` Bradley M. Kuhn
2022-05-25 21:50 ` J Lovejoy
2022-05-25 22:29 ` Bradley M. Kuhn
2022-05-23 21:22 ` Thomas Gleixner
2022-05-25 16:57 ` Luis Chamberlain
2022-05-25 20:51 ` Thomas Gleixner
2022-05-25 23:53 ` Luis Chamberlain
2022-05-23 21:27 ` Thomas Gleixner
2022-05-25 16:43 ` Luis Chamberlain
2022-05-25 17:05 ` Bird, Tim
2022-05-25 18:11 ` Luis Chamberlain
2022-05-25 19:05 ` Bird, Tim
2022-05-25 19:44 ` Luis Chamberlain
2022-05-25 22:16 ` Thomas Gleixner
2022-06-02 4:11 ` Bird, Tim
2022-06-02 6:20 ` gregkh
2022-06-02 19:41 ` Luis Chamberlain
2022-06-02 19:30 ` Luis Chamberlain
2021-10-29 18:44 ` [PATCH v9 2/6] testing: use the copyleft-next-0.3.1 SPDX tag Luis Chamberlain
2021-10-29 18:44 ` [PATCH v9 3/6] selftests: add tests_sysfs module Luis Chamberlain
2021-12-03 15:29 ` Greg KH
2021-12-09 1:48 ` Luis Chamberlain
2021-12-10 21:39 ` Luis Chamberlain
2021-12-14 19:31 ` [copyleft-next] " Richard Fontana
2022-05-22 14:37 ` Thomas Gleixner
2022-05-22 14:47 ` Greg KH
2022-05-22 15:06 ` Thomas Gleixner
2022-05-23 19:37 ` Luis Chamberlain
2021-10-29 18:44 ` [PATCH v9 4/6] kernfs: add initial failure injection support Luis Chamberlain
2021-10-29 18:44 ` [PATCH v9 5/6] test_sysfs: add support to use kernfs failure injection Luis Chamberlain
2021-10-29 18:45 ` [PATCH v9 6/6] kernel/module: add documentation for try_module_get() Luis Chamberlain
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=87h75g0xbm.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Christopher.DeNicolo@suse.com \
--cc=Ciaran.Farrell@suse.com \
--cc=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=copyleft-next@lists.fedorahosted.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=fontana@sharpeleven.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jeyu@kernel.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kuno@frob.nl \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=mcgrof@kernel.org \
--cc=minchan@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tj@kernel.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).