b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH 3/6] batctl: Import Linux's LICENSES/preferred/MIT
Date: Sun, 19 Nov 2017 15:05:50 +0100	[thread overview]
Message-ID: <20171119140553.24435-4-sven@narfation.org> (raw)
In-Reply-To: <20171119140553.24435-1-sven@narfation.org>

The MIT license is used by batctl for some of the code. Copy the Linux
license reference file with SPDX header for completeness sake.

Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
 LICENSES/preferred/MIT | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 LICENSES/preferred/MIT

diff --git a/LICENSES/preferred/MIT b/LICENSES/preferred/MIT
new file mode 100644
index 0000000..f33a68c
--- /dev/null
+++ b/LICENSES/preferred/MIT
@@ -0,0 +1,30 @@
+Valid-License-Identifier: MIT
+SPDX-URL: https://spdx.org/licenses/MIT.html
+Usage-Guide:
+  To use the MIT License put the following SPDX tag/value pair into a
+  comment according to the placement guidelines in the licensing rules
+  documentation:
+    SPDX-License-Identifier: MIT
+License-Text:
+
+MIT License
+
+Copyright (c) <year> <copyright holders>
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the "Software"),
+to deal in the Software without restriction, including without limitation
+the rights to use, copy, modify, merge, publish, distribute, sublicense,
+and/or sell copies of the Software, and to permit persons to whom the
+Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.
-- 
2.11.0


  parent reply	other threads:[~2017-11-19 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 14:05 [B.A.T.M.A.N.] [PATCH 0/6] batctl: License cleanup Sven Eckelmann
2017-11-19 14:05 ` [B.A.T.M.A.N.] [PATCH 1/6] batctl: Add GPL-2.0 as Linux's LICENSES/preferred/GPL-2.0 Sven Eckelmann
2017-11-19 14:05 ` [B.A.T.M.A.N.] [PATCH 2/6] batctl: Add License-Filename to GPL-2.0 files Sven Eckelmann
2017-11-19 14:05 ` Sven Eckelmann [this message]
2017-11-19 14:05 ` [B.A.T.M.A.N.] [PATCH 4/6] batctl: Add SPDX license identifier above copyright header Sven Eckelmann
2017-11-19 14:05 ` [B.A.T.M.A.N.] [PATCH 5/6] batctl: Mark remaining files as GPL-2.0 Sven Eckelmann
2017-11-19 14:05 ` [B.A.T.M.A.N.] [PATCH 6/6] batctl: Change batman_adv.h license to MIT Sven Eckelmann
2017-12-01 13:40 ` [B.A.T.M.A.N.] [PATCH v2 5/6] batctl: Mark remaining files as GPL-2.0 Sven Eckelmann
2017-12-06 10:52 ` [B.A.T.M.A.N.] [PATCH 0/6] batctl: License cleanup Sven Eckelmann

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=20171119140553.24435-4-sven@narfation.org \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.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;
as well as URLs for NNTP newsgroup(s).