From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] CHANGES: extend 2016.11-rc1 changelog
Date: Thu, 3 Nov 2016 22:57:35 +0100 [thread overview]
Message-ID: <20161103225735.5b27a6fb@free-electrons.com> (raw)
In-Reply-To: <20161103214929.22442-1-arnout@mind.be>
Hello,
On Thu, 3 Nov 2016 22:49:29 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> - Longer explanation of multi-BR2_EXTERNAL
> - Mention nobody UID 99 -> 65534 change
> - Mention removal of BR2_DEPRECATED
> - Mention use of system cmake
> - Mention new dependency on ExtUtils::MakeMaker. The other perl
> dependencies are not mentioned since they only apply if mpv is built.
> - Mention the $(STAGING_DIR)/$(O) check.
> - Mention unsafe path detection in -isystem etc.
> - Mention linux-tools split.
> - Mention changes in legal-info.
> - Mention that pseudo is used instead of fakeroot.
> - Correct the info of toolchainfile.cmake: it still sets cflags but it
> doesn't force them anymore (doesn't append).
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> CHANGES | 57 +++++++++++++++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 49 insertions(+), 8 deletions(-)
Applied to master, thanks a lot for the additional writeup!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-03 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 21:49 [Buildroot] [PATCH] CHANGES: extend 2016.11-rc1 changelog Arnout Vandecappelle
2016-11-03 21:57 ` Thomas Petazzoni [this message]
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=20161103225735.5b27a6fb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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