From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-doc <linux-doc@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jonas Oberg <jonas@fsfe.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Matthew Wilcox <willy@infradead.org>
Subject: [PATCH v2 0/2] COPYING: create a new file with points to the Kernel license files
Date: Fri, 23 Mar 2018 06:51:04 -0300 [thread overview]
Message-ID: <20180323095106.23108-1-mchehab@s-opensource.com> (raw)
The contents of COPYING file is now duplicated at two other
files under LICENSE:
LICENSES/preferred/GPL-2.0
LICENSES/exceptions/Linux-syscall-note
Also, a new file was added, with describes how SPDX should work at
the Kernel source files:
Documentation/process/license-rules.rst
Instead fo having it copying the contents of two files, and not
even mentioning the third one, replace it by a file whose content
points to the other tree files, preserving the Kernel's license.
Adjust license-rules.rst accordingly.
No license changes.
NOTE
====
In order to make the diff easier to read, I broke it into two patches.
Feel free to merge both when merging if you want.
Mauro Carvalho Chehab (2):
COPYING: create a new file with points to the Kernel license files
COPYING: use the new text with points to the license files
COPYING | 358 +-------------------------------
Documentation/process/license-rules.rst | 20 +-
2 files changed, 21 insertions(+), 357 deletions(-)
--
2.14.3
next reply other threads:[~2018-03-23 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 9:51 Mauro Carvalho Chehab [this message]
2018-03-23 9:51 ` [PATCH v2 1/2] " Mauro Carvalho Chehab
2018-03-23 10:26 ` Greg Kroah-Hartman
2018-03-23 9:51 ` [PATCH v2 2/2] COPYING: use the new text with points to the " Mauro Carvalho Chehab
2018-03-23 18:29 ` [PATCH v2 0/2] COPYING: create a new file with points to the Kernel " Jonathan Corbet
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=20180323095106.23108-1-mchehab@s-opensource.com \
--to=mchehab@s-opensource.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jonas@fsfe.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=pombredanne@nexb.com \
--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
all inboxes | Powered by JetHome®