From: Luis Chamberlain <mcgrof@kernel.org>
To: "Bird, Tim" <Tim.Bird@sony.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Richard Fontana <fontana@sharpeleven.org>,
"tj@kernel.org" <tj@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"jeyu@kernel.org" <jeyu@kernel.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"joe@perches.com" <joe@perches.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"minchan@kernel.org" <minchan@kernel.org>,
"linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Goldwyn Rodrigues <rgoldwyn@suse.com>, Kuno Woudt <kuno@frob.nl>,
"copyleft-next@lists.fedorahosted.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: Thu, 2 Jun 2022 12:30:50 -0700 [thread overview]
Message-ID: <YpkP6kExQcQZd2/O@bombadil.infradead.org> (raw)
In-Reply-To: <BYAPR13MB2503DAC31B8B5CC69F8FECD3FDDE9@BYAPR13MB2503.namprd13.prod.outlook.com>
On Thu, Jun 02, 2022 at 04:11:16AM +0000, Bird, Tim wrote:
> I don't think that the Linux kernel should be used for license promotion, but if it is,
> then it should be used to promote GPL-v2-only.
I already *used* copyleft-next on Linux on a dual licensed manner, the
patches in question are about using SPDX to simpllify things and adaopt
the SPDX annotations.
And, to re-iterate once more, I'm using copyeft-next as that is *my*
license of choice for *any* new software projects I use and I want to enable
cross prolination between them. I have been doing this since I wrote
CRDA many years ago. I have many reasons for using copyleft-next and I've
listed many of the reasons why a free software developer would care to enable
this cross polination but yet again you seem to be disregarding all that.
This is similar to how 2-cluase BSD is compatible with the GPL
and is used for cross polination to BSDs even though in practice
a lot of that cross polination may not happen.
There are practical uses here and I've been using this license for years now
and I have no intention on stopping.
Luis
next prev parent reply other threads:[~2022-06-02 19:31 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
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 [this message]
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=YpkP6kExQcQZd2/O@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=Christopher.DeNicolo@suse.com \
--cc=Ciaran.Farrell@suse.com \
--cc=Tim.Bird@sony.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=minchan@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--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).