From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org,
"Steven Rostedt (VMware)" <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Frank A. Cancio Bello" <frank@generalsoftwareinc.com>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: [PATCH v3 0/2] use SPDX also for GFDL documents
Date: Wed, 9 Sep 2020 07:14:31 +0200 [thread overview]
Message-ID: <cover.1599628249.git.mchehab+huawei@kernel.org> (raw)
There are 438 document files that were licensed under the
free versions of GNU Free Document License.
The free versions are the one that doesn't contain invariant
parts.
The first patch adds the license files. As newer documents
aren't supposed to use them without being dual-licensed
with GPLv2, add them under LICENSE/deprecated.
The second patch replaces a boilerplate text from
ring-buffer-design.rst by the corresponding SPDX header.
The other documents are all under Documentation/uapi/media.
A separate patchset, to be merged via the linux-media tree
will cover those.
---
v3:
- Added Valid-License-Identifier, SPDX_URL, Usage-Guide and License-Text
meta-tags.
Mauro Carvalho Chehab (2):
LICENSE: add GFDL deprecated licenses
docs: trace: ring-buffer-design.rst: use the new SPDX tag
Documentation/trace/ring-buffer-design.rst | 26 +-
LICENSES/deprecated/GFDL-1.1 | 377 +++++++++++++++++++
LICENSES/deprecated/GFDL-1.2 | 417 +++++++++++++++++++++
3 files changed, 795 insertions(+), 25 deletions(-)
create mode 100644 LICENSES/deprecated/GFDL-1.1
create mode 100644 LICENSES/deprecated/GFDL-1.2
--
2.26.2
next reply other threads:[~2020-09-09 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 5:14 Mauro Carvalho Chehab [this message]
2020-09-09 5:14 ` [PATCH v3 1/2] LICENSE: add GFDL deprecated licenses Mauro Carvalho Chehab
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=cover.1599628249.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=corbet@lwn.net \
--cc=frank@generalsoftwareinc.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=rostedt@goodmis.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 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).