All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 1/3] LICENSES: Add the CC-BY-4.0 license
Date: Fri, 4 Dec 2020 13:23:43 +0100	[thread overview]
Message-ID: <X8oqTyRNKMHChbA7@kroah.com> (raw)
In-Reply-To: <7115b6c20ae3e6db0370fe4002dd586011205e1c.1607063223.git.linux@leemhuis.info>

On Fri, Dec 04, 2020 at 07:43:48AM +0100, Thorsten Leemhuis wrote:
> Add the full text of the CC-BY-4.0 license to the kernel tree as well as
> the required tags for reference and tooling.
> 
> The license text was copied directly from the following url, but for
> clarification a 'Creative Commons' was added before 'Attribution 4.0
> International' in the first line:
> https://creativecommons.org/licenses/by/4.0/legalcode.txt
> 
> CC-BY-4.0 is GPLv2 compatible, but when for example used for the
> kernel's documentation it can easily happen that sphinx during
> processing combines it with text or code from files using a more
> restrictive license[1]. This bears pitfalls, hence point that risk out
> and suggest to only use this license in combination with the GPLv2.
> 
> [1] https://lkml.kernel.org/r/20201201144314.GA14256@lst.de
> 
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CC: Christoph Hellwig <hch@lst.de>
> ---
>  LICENSES/dual/CC-BY-4.0 | 410 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 410 insertions(+)
>  create mode 100644 LICENSES/dual/CC-BY-4.0

Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  reply	other threads:[~2020-12-04 12:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  6:43 [PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten") Thorsten Leemhuis
2020-12-04  6:43 ` [PATCH v4 1/3] LICENSES: Add the CC-BY-4.0 license Thorsten Leemhuis
2020-12-04 12:23   ` Greg Kroah-Hartman [this message]
2020-12-04 21:26     ` Jonathan Corbet
2020-12-04  6:43 ` [PATCH v4 2/3] docs: Add a new text describing how to report bugs Thorsten Leemhuis
2020-12-04  6:43 ` [PATCH v4 3/3] docs: make reporting-bugs.rst obsolete Thorsten Leemhuis
2020-12-08 17:44 ` [PATCH v4 0/3] New documentation text describing how to report issues (aka "reporting-bugs rewritten") Jonathan Corbet
2020-12-09  5:25   ` Thorsten Leemhuis

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=X8oqTyRNKMHChbA7@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=hch@lst.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.