From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-spdx@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Subject: Re: [PATCH 18/22] docs: trace: ring-buffer-design.txt: convert to ReST format
Date: Mon, 15 Jun 2020 10:48:10 -0700 [thread overview]
Message-ID: <4e00b2fa91f1f818de4658f2695d4b433852959d.camel@perches.com> (raw)
In-Reply-To: <c11ee0be2bf63626887d7cd38e7572b31e2a2ce2.1592203650.git.mchehab+huawei@kernel.org>
On Mon, 2020-06-15 at 08:50 +0200, Mauro Carvalho Chehab wrote:
> - Just like some media documents, this file is dual licensed
> with GPL and GFDL. As right now the GFDL SPDX definition is
> bogus (as it doesn't tell anything about invariant parts),
> let's not use SPDX here. Let's use, instead, the same test
> as we have on media.
[]
> diff --git a/Documentation/trace/ring-buffer-design.txt b/Documentation/trace/ring-buffer-design.rst
> []
> +.. Or, alternatively,
> +..
> +.. b) Permission is granted to copy, distribute and/or modify this
> +.. document under the terms of the GNU Free Documentation License,
> +.. Version 1.1 or any later version published by the Free Software
> +.. Foundation, with no Invariant Sections, no Front-Cover Texts
> +.. and no Back-Cover Texts. A copy of the license is available at
> +.. https://www.gnu.org/licenses/old-licenses/fdl-1.2.html
Use of a version 1.1 reference with a 1.2 link.
Perhaps the link should be:
https://www.gnu.org/licenses/old-licenses/fdl-1.1.html
> +..
> +.. TODO: replace it to GPL-2.0 OR GFDL-1.2-or-later WITH no-invariant-sections
Is there some reason a new GFDL entry has not yet been added
to the LICENSES directory?
next parent reply other threads:[~2020-06-15 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1592203650.git.mchehab+huawei@kernel.org>
[not found] ` <c11ee0be2bf63626887d7cd38e7572b31e2a2ce2.1592203650.git.mchehab+huawei@kernel.org>
2020-06-15 17:48 ` Joe Perches [this message]
2020-06-16 7:19 ` [PATCH 18/22] docs: trace: ring-buffer-design.txt: convert to ReST format 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=4e00b2fa91f1f818de4658f2695d4b433852959d.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=mchehab+huawei@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).