Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] COPYING: add exception about patch licensing
Date: Thu, 25 Feb 2016 20:42:00 +0100	[thread overview]
Message-ID: <20160225194200.GB5870@free.fr> (raw)
In-Reply-To: <1456401075-16948-2-git-send-email-luca@lucaceresoli.net>

Luca, All,

On 2016-02-25 12:51 +0100, Luca Ceresoli spake thusly:
> Several people have been asking what is the license of the patches
> provided by Buildroot. COPYING is the authoritative place to state it.
> 
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Steve Calfee <stevecalfee@gmail.com>

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Thanks! :-)

Regards,
Yann E. MORIN.

> ---
> Changes v2 -> v3:
>  - Rewrite it entirely based on comments on the mailing list (Yann,
>    Arnout, Thomas, Peter, Steve).
> 
> Changes v1 -> v2:
>  - Rewrite it almost entirely (Arnout, Thomas).
> ---
>  COPYING | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/COPYING b/COPYING
> index d511905..0c018b0 100644
> --- a/COPYING
> +++ b/COPYING
> @@ -1,3 +1,19 @@
> +With the exceptions below, Buildroot is distributed under the terms of
> +the GNU General Public License, reproduced below; either version 2 of
> +the License, or (at your option) any later version.
> +
> +Some files in Buildroot contain a different license statement. Those
> +files are licensed under the license contained in the file itself.
> +
> +Buildroot also bundles patch files, which are applied to the sources
> +of the various packages. Those patches are not covered by the license
> +of Buildroot. Instead, they are covered by the license of the software
> +to which the patches are applied. When said software is available
> +under multiple licenses, the Buildroot patches are only provided under
> +the publicly accessible licenses.
> +
> +-----------------------------------------------------------------
> +
>  		    GNU GENERAL PUBLIC LICENSE
>  		       Version 2, June 1991
>  
> -- 
> 1.9.1
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2016-02-25 19:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 11:51 [Buildroot] [PATCH v3 0/2] Patch file clarification & Co Luca Ceresoli
2016-02-25 11:51 ` [Buildroot] [PATCH v3 1/2] COPYING: add exception about patch licensing Luca Ceresoli
2016-02-25 12:40   ` Thomas Petazzoni
2016-02-25 19:42   ` Yann E. MORIN [this message]
2016-02-26 18:51   ` Peter Korsgaard
2016-02-25 11:51 ` [Buildroot] [PATCH v3 2/2] docs/manual: add section " Luca Ceresoli
2016-02-25 20:16   ` Yann E. MORIN
2016-02-26 22:08     ` Luca Ceresoli

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=20160225194200.GB5870@free.fr \
    --to=yann.morin.1998@free.fr \
    --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