From: Christoph Hellwig <hch@lst.de>
To: Jonathan Corbet <corbet@lwn.net>, Thomas Gleixner <tglx@linutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] docs: Don't reference the ZLib license in license-rules.rst
Date: Tue, 30 Apr 2019 06:51:28 -0400 [thread overview]
Message-ID: <20190430105130.24500-2-hch@lst.de> (raw)
In-Reply-To: <20190430105130.24500-1-hch@lst.de>
We never had a file called LICENSES/other/ZLib in the tree, so don't
reference it. Instead mention the GPL v1 as an (bad) example.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
Documentation/process/license-rules.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/process/license-rules.rst b/Documentation/process/license-rules.rst
index 6b09033a8e9e..ade495fe6811 100644
--- a/Documentation/process/license-rules.rst
+++ b/Documentation/process/license-rules.rst
@@ -255,9 +255,9 @@ kernel, can be broken down into:
Contains the Internet Systems Consortium license text and the required
metatags::
- LICENSES/other/ZLib
+ LICENSES/other/GPL-1.0
- Contains the ZLIB license text and the required metatags.
+ Contains the GPL version 1 license text and the required metatags.
Metatags:
--
2.20.1
next prev parent reply other threads:[~2019-04-30 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 10:51 clarify other licenses in LICENSES/ Christoph Hellwig
2019-04-30 10:51 ` Christoph Hellwig [this message]
2019-04-30 10:51 ` [PATCH 2/3] LICENSES: Clearly mark dual license only licenses Christoph Hellwig
2019-04-30 10:51 ` [PATCH 3/3] LICENSES: Rename other to deprecated Christoph Hellwig
2019-05-14 10:26 ` Borislav Petkov
2019-05-14 13:49 ` Christoph Hellwig
2019-05-14 14:10 ` Borislav Petkov
2019-04-30 11:41 ` clarify other licenses in LICENSES/ Greg Kroah-Hartman
2019-05-03 12:34 ` 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=20190430105130.24500-2-hch@lst.de \
--to=hch@lst.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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 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.