From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 5/5] legal-info: explicitly state how patches are licensed
Date: Mon, 1 Feb 2016 23:19:56 +0100 [thread overview]
Message-ID: <1454365196-26319-6-git-send-email-luca@lucaceresoli.net> (raw)
In-Reply-To: <1454365196-26319-1-git-send-email-luca@lucaceresoli.net>
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
---
| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--git a/support/legal-info/README.header b/support/legal-info/README.header
index 0b5aa66..316f799 100644
--- a/support/legal-info/README.header
+++ b/support/legal-info/README.header
@@ -18,7 +18,7 @@ This material is composed of the following items.
sources/ subdirectory (except for the non-redistributable packages, which
have not been saved). Patches that were applied are also saved, along
with a file named 'series' that lists the patches in the order they were
- applied.
+ applied. Patches are under the same license as the original package.
* A manifest file listing the configured packages and related information.
* The license text of the packages; they have been saved in the licenses/
subdirectory.
--
1.9.1
next prev parent reply other threads:[~2016-02-01 22:19 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
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 ` Luca Ceresoli [this message]
2016-03-06 15:14 ` [Buildroot] [PATCH v2 5/5] legal-info: explicitly state how patches are licensed 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=1454365196-26319-6-git-send-email-luca@lucaceresoli.net \
--to=luca@lucaceresoli.net \
--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.