All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] docs/manual: document MPL licenses
Date: Thu, 16 Mar 2017 17:24:00 +0530	[thread overview]
Message-ID: <1489665241-14942-2-git-send-email-rahul.bedarkar@imgtec.com> (raw)
In-Reply-To: <1489665241-14942-1-git-send-email-rahul.bedarkar@imgtec.com>

Many packages are provided under MPL v1.1 and v2.0. Document it under
License abbreviations section.

Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
---
Note: There appears to be Mozilla Public License Version 1.0 as well. But I can't
find link to web page on mozilla.org site. So it is not documented currently.

 docs/manual/legal-notice.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index 1e1e2b3..df82fd2 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -151,6 +151,12 @@ Buildroot, with the name used in the manifest files:
 * `ISC`:
   https://opensource.org/licenses/ISC[
   ISC License];
+* `MPLv1.1`:
+  https://www.mozilla.org/en-US/MPL/1.1[
+  Mozilla Public License Version 1.1]
+* `MPLv2.0`:
+  https://www.mozilla.org/en-US/MPL/2.0[
+  Mozilla Public License Version 2.0]
 
 [[legal-info-buildroot]]
 === Complying with the Buildroot license
-- 
2.6.2

  reply	other threads:[~2017-03-16 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 11:53 [Buildroot] [PATCH 1/3] docs/manual: document ISC license Rahul Bedarkar
2017-03-16 11:54 ` Rahul Bedarkar [this message]
2017-03-16 11:54 ` [Buildroot] [PATCH 3/3] taglib: update homepage link Rahul Bedarkar
2017-03-17 23:40   ` Peter Korsgaard
2017-03-16 15:58 ` [Buildroot] [PATCH 1/3] docs/manual: document ISC license Peter Korsgaard

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=1489665241-14942-2-git-send-email-rahul.bedarkar@imgtec.com \
    --to=rahul.bedarkar@imgtec.com \
    --cc=buildroot@busybox.net \
    /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.