From: Adrian Bunk <bunk@stusta.de>
To: Martin Siegumfeldt <mns@gomspace.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe,thud][PATCH 0/6] libiio: backports from master
Date: Tue, 5 Nov 2019 15:55:12 +0200 [thread overview]
Message-ID: <20191105135512.GB20425@localhost> (raw)
In-Reply-To: <20191105120031.6579-1-mns@gomspace.com>
On Tue, Nov 05, 2019 at 01:00:25PM +0100, Martin Siegumfeldt wrote:
> Backport libiio patches from master bumping libiio to v0.18 and
Upgrading on an upstream stable branch can be OK,
especially when this is the lowest risk way to fix CVEs.
But upgrading to new releases on the master branch is usually not worth
the regression risk - the default is to avoid changes in OE stable branches.
> allows building python3 bindings
>...
No new features in OE stable branches.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-11-05 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 12:00 [meta-oe,thud][PATCH 0/6] libiio: backports from master Martin Siegumfeldt
2019-11-05 12:00 ` [meta-oe,thud][PATCH 1/6] Bump libiio version to 0.15 Martin Siegumfeldt
2019-11-05 12:00 ` [meta-oe, thud][PATCH 2/6] Revert "libiio: fix build of python bindins" Martin Siegumfeldt
2019-11-05 12:00 ` [meta-oe, thud][PATCH 3/6] libiio: allow python3 bindings to be built Martin Siegumfeldt
2019-11-05 12:00 ` [meta-oe,thud][PATCH 4/6] libiio: bump to version 0.18+ Martin Siegumfeldt
2019-11-05 13:19 ` [meta-oe,thud][PATCH 0/6] libiio: backports from master Martin Siegumfeldt
2019-11-05 13:55 ` Adrian Bunk [this message]
2019-11-05 13:57 ` Adrian Bunk
2019-11-06 9:14 ` Martin Siegumfeldt
2019-11-06 18:23 ` Adrian Bunk
2019-11-07 8:52 ` Martin Siegumfeldt
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=20191105135512.GB20425@localhost \
--to=bunk@stusta.de \
--cc=mns@gomspace.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.