From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] docs/manual/legal-notice.txt: update list of non-saved material
Date: Sat, 18 Jan 2020 18:56:29 +0100 [thread overview]
Message-ID: <20200118175629.GD32369@scaer> (raw)
In-Reply-To: <20200118161820.12412-1-luca@lucaceresoli.net>
Luca, All,
On 2020-01-18 17:18 +0100, Luca Ceresoli spake thusly:
> This list dates back to 2012. Since a long time now Buildroot saves the
> patches applied as well as the actual source code for some external
> toolchains. Update the manual accordingly.
>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Both applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> docs/manual/legal-notice.txt | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
> index 69753282ec30..179aa6b1798e 100644
> --- a/docs/manual/legal-notice.txt
> +++ b/docs/manual/legal-notice.txt
> @@ -67,9 +67,8 @@ for packages released under BSD-like licenses, that you are not required to
> redistribute in source form.
>
> Moreover, due to technical limitations, Buildroot does not produce some
> -material that you will or may need, such as the toolchain source code and the
> -Buildroot source code itself (including patches to packages for which source
> -distribution is required).
> +material that you will or may need, such as the toolchain source code for
> +some of the external toolchains and the Buildroot source code itself.
> When you run +make legal-info+, Buildroot produces warnings in the +README+
> file to inform you of relevant material that could not be saved.
>
> --
> 2.25.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-01-18 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 16:18 [Buildroot] [PATCH 1/2] docs/manual/legal-notice.txt: update list of non-saved material Luca Ceresoli
2020-01-18 16:18 ` [Buildroot] [PATCH 2/2] core/legal-info: update list of saved material in README Luca Ceresoli
2020-03-05 20:14 ` Peter Korsgaard
2020-01-18 17:56 ` Yann E. MORIN [this message]
2020-03-05 20:14 ` [Buildroot] [PATCH 1/2] docs/manual/legal-notice.txt: update list of non-saved material Peter Korsgaard
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=20200118175629.GD32369@scaer \
--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