From: <Mikko.Rapeli@bmw.de>
To: <schnitzeltony@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [thud][PATCH] Revert "boost: update to 1.69.0"
Date: Tue, 19 Mar 2019 07:52:06 +0000 [thread overview]
Message-ID: <20190319075206.GK20077@hiutale> (raw)
In-Reply-To: <CALbNGRT1_qD8LYEP7X7JexnEOW7AsC84ceatZ3BLgECoo7vixQ@mail.gmail.com>
On Mon, Mar 18, 2019 at 06:03:05PM +0100, Andreas Müller wrote:
> On Mon, Mar 18, 2019 at 5:45 PM Armin Kuster <akuster808@gmail.com> wrote:
> >
> > This reverts commit a384248938ea9db096866bf4ec8678d35ca62a12.
> >
> > This package update slipped in doing the maint process. Removing it.
<snip>
> Just my opinion - don't consider this as NAK.
>
> * I already fixed the recipes that failed for me. For at least one the
> change is no more compatible to 1.68.0.
> * This makes PV going backwards
>
> Thanks for addressing - what do others think?
I'm not using thud yet, but updating boost in stable branch would break
too many things and I would have to revert that change in our trees. Some boost
updates are in the end quite trivial and just require recompiling
everything but still, I would prefer that boost is not updated in stable
branches unless there is a huge security/stability issue with the old version.
Hope this helps,
-Mikko
next prev parent reply other threads:[~2019-03-19 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 16:45 [thud][PATCH] Revert "boost: update to 1.69.0" Armin Kuster
2019-03-18 17:03 ` Andreas Müller
2019-03-19 7:52 ` Mikko.Rapeli [this message]
2019-03-24 18:01 ` Martin Jansa
2019-03-24 18:45 ` akuster808
2019-03-24 18:48 ` Martin Jansa
2019-04-02 7:18 ` Martin Jansa
2019-04-02 17:51 ` akuster808
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=20190319075206.GK20077@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@gmail.com \
/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