Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] docs/manual: document format for specifying licenses
Date: Sun, 6 Mar 2016 21:54:38 +0100	[thread overview]
Message-ID: <20160306215438.4d75baf0@free-electrons.com> (raw)
In-Reply-To: <1453698340-13777-1-git-send-email-rahul.bedarkar@imgtec.com>

Dear Rahul Bedarkar,

On Mon, 25 Jan 2016 10:35:40 +0530, Rahul Bedarkar wrote:
> +  ** If the package is released under multiple licenses, then +comma+ separate

I found the wording "If the package is released under multiple
licenses" as potentially confusing, as it could be understood as the
dual licensing case. So I've changed that to:

+  ** If different parts of the package are released under different
+  licenses

Which I believe is clearer.

> +  licenses (e.g. +`LIBFOO_LICENSE = GPLv2+, LGPLv2.1+`+). If there is clear
> +  distinction between which component is licensed under what license, then
> +  annotate the license with that component
> +  (e.g. +`LIBFOO_LICENSE = GPLv2+ (programs), LGPLv2.1+ (libraries)`+).

I've explicited: "annonate the license with that component between
parenthesis".

And applied to master. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2016-03-06 20:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25  5:05 [Buildroot] [PATCH v2 1/1] docs/manual: document format for specifying licenses Rahul Bedarkar
2016-02-04  4:09 ` Rahul Bedarkar
2016-03-06 20:54 ` Thomas Petazzoni [this message]

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=20160306215438.4d75baf0@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox