From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boost: bump to 1.65.1
Date: Sat, 21 Oct 2017 15:29:37 +0200 [thread overview]
Message-ID: <20171021152937.438dfae9@windsurf> (raw)
In-Reply-To: <20171017204407.27704-1-Adamduskett@outlook.com>
Hello,
On Tue, 17 Oct 2017 16:44:07 -0400, Adam Duskett wrote:
> Other changes:
> - The coroutine2 library has been removed. As such it has been removed
> from the boost.mk file, the boost Config.in file, and a new entry has
> been added to Config.in.legacy explaining that it has been removed.
>
> - Add LICENSE_1_0.txt sha256sum to boost.hash
>
> Signed-off-by: Adam Duskett <Adamduskett@outlook.com>
> ---
> Config.in.legacy | 6 ++++++
> package/boost/Config.in | 4 ----
> package/boost/boost.hash | 7 +++++--
> package/boost/boost.mk | 9 ++++-----
> 4 files changed, 15 insertions(+), 11 deletions(-)
Following the comments from the reviewers (thanks to them!), I've:
- Reworded the commit log to be correct about what happened to
coroutine2
- Removed the Config.in.legacy handling: even though we're removing an
option, coroutine2 support is now unconditionally present in Boost,
so having legacy handling for this doesn't make much sense.
Applied with those changes. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-10-21 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 20:44 [Buildroot] [PATCH 1/1] boost: bump to 1.65.1 Adam Duskett
2017-10-18 18:48 ` Jörg Krause
2017-10-19 16:18 ` Henrique Marks
2017-10-19 19:49 ` Adam Duskett
2017-10-20 15:57 ` Henrique Marks
2017-10-20 16:23 ` Bernd Kuhls
2017-10-20 17:15 ` Henrique Marks
2017-10-21 13:29 ` 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=20171021152937.438dfae9@windsurf \
--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