From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt
Date: Wed, 17 Aug 2016 18:01:09 +0200 [thread overview]
Message-ID: <1471449670-13421-2-git-send-email-romain.naour@gmail.com> (raw)
In-Reply-To: <1471449670-13421-1-git-send-email-romain.naour@gmail.com>
Since 1273636fc686cd788b6de87be75dd0726cf8676c applied patches are also
saved.
Signed-off-by: Romain Naour <romain.naour@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Arnout Vandecappelle <arnout@mind.be>
---
docs/manual/legal-notice.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
index 0572dae..a4911f7 100644
--- a/docs/manual/legal-notice.txt
+++ b/docs/manual/legal-notice.txt
@@ -41,9 +41,9 @@ There you will find:
+host-sources/+ subdirectories for target and host packages respectively.
The source code for packages that set +<PKG>_REDISTRIBUTE = NO+ will not be
saved.
- Patches applied to some packages by Buildroot are distributed with the
- Buildroot sources and are not duplicated in the +sources/+ and +host-sources/+
- subdirectories.
+ Patches that were applied are also saved, along with a file named +series+
+ that lists the patches in the order they were applied. Patches are under the
+ same license as the files that they modify.
* A manifest file (one for host and one for target packages) listing the
configured packages, their version, license and related information.
Some of this information might not be defined in Buildroot; such items are
--
2.5.5
next prev parent reply other threads:[~2016-08-17 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 16:01 [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Romain Naour
2016-08-17 16:01 ` Romain Naour [this message]
2016-08-17 17:19 ` [Buildroot] [PATCH v2 2/3] docs: update legal-notice.txt Yann E. MORIN
2016-08-19 14:20 ` Thomas Petazzoni
2016-08-17 16:01 ` [Buildroot] [PATCH v2 3/3] docs: libtool patches are not handled by legal-info infrastructure Romain Naour
2016-08-17 17:22 ` Yann E. MORIN
2016-08-19 21:34 ` Thomas Petazzoni
2016-08-19 21:39 ` Yann E. MORIN
2016-08-18 21:59 ` [Buildroot] [PATCH v2 1/3] core/pkg-autotools: don't use APPLY_PATCHES for libtool patches Thomas Petazzoni
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=1471449670-13421-2-git-send-email-romain.naour@gmail.com \
--to=romain.naour@gmail.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