From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] COPYING: add exception about patch licensing
Date: Thu, 25 Feb 2016 11:57:40 +0100 [thread overview]
Message-ID: <8737shxdjv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56C750A1.5050908@lucaceresoli.net> (Luca Ceresoli's message of "Fri, 19 Feb 2016 18:28:01 +0100")
>>>>> "Luca" == Luca Ceresoli <luca@lucaceresoli.net> writes:
Hi,
> Here's what I've been able to come up with so far. It's basically:
> - the sum of the present thread, plus
> - a reduced and modified version of the preamble suggested in the
> GNU GPL itself (section "How to Apply These Terms to Your New
> Programs"), plus
> - the statement that BR is GPLv2+ except where differently stated,
> as Arnout suggested.
> I'm sure this needs further discussion and improvements.
> -------------------------8<----------------------
> 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.
This sounds good to me. Do anyone disagree or can this be committed to
master?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-02-25 10:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 22:19 [Buildroot] [PATCH v2 0/5] Patch file clarification & Co Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 1/5] Update copyright year Luca Ceresoli
2016-02-01 22:24 ` Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 2/5] docs/manual: slightly clarify patch licensing Luca Ceresoli
2016-02-02 8:58 ` Yann E. MORIN
2016-02-03 22:53 ` Yann E. MORIN
2016-02-10 22:15 ` Arnout Vandecappelle
2016-02-25 10:50 ` Peter Korsgaard
2016-02-01 22:19 ` [Buildroot] [PATCH v2 3/5] COPYING: add exception about " Luca Ceresoli
2016-02-01 22:31 ` Thomas Petazzoni
2016-02-03 23:02 ` Yann E. MORIN
2016-02-03 23:57 ` Arnout Vandecappelle
2016-02-04 20:42 ` Yann E. MORIN
2016-02-04 21:08 ` Thomas Petazzoni
2016-02-04 21:40 ` Yann E. MORIN
2016-02-04 21:51 ` Thomas Petazzoni
2016-02-04 22:28 ` Steve Calfee
2016-02-05 9:25 ` Luca Ceresoli
2016-02-05 12:07 ` Peter Korsgaard
2016-02-10 22:35 ` Arnout Vandecappelle
2016-02-19 17:28 ` Luca Ceresoli
2016-02-25 10:57 ` Peter Korsgaard [this message]
2016-02-25 11:53 ` Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 4/5] docs/manual: add section " Luca Ceresoli
2016-02-03 23:34 ` Yann E. MORIN
2016-02-26 22:08 ` Luca Ceresoli
2016-02-26 22:28 ` Yann E. MORIN
2016-02-10 22:37 ` Arnout Vandecappelle
2016-02-01 22:19 ` [Buildroot] [PATCH v2 5/5] legal-info: explicitly state how patches are licensed Luca Ceresoli
2016-03-06 15:14 ` Thomas Petazzoni
2016-03-06 22:52 ` Luca Ceresoli
2016-03-06 22:56 ` Yann E. MORIN
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=8737shxdjv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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