From: "Steve Sakoman" <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/2] Patch review
Date: Mon, 8 Mar 2021 06:47:16 -1000 [thread overview]
Message-ID: <cover.1615221849.git.steve@sakoman.com> (raw)
Please review this next set of patches for dunfell and have comments back by
end of day Wednesday.
Passed a-full and meta-oe on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/1948
https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/1014
The following changes since commit cf22f3831488b346195e049ace92e153d18660db:
meta/recipes-core: Add HOMEPAGE / DESCRIPTION (2021-03-05 04:40:01 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-nut
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Michael Halstead (2):
yocto-uninative.inc: version 2.11 updates glibc to 2.33
yocto-uninative.inc: version 3.0 incorporate seccomp filter workaround
meta/conf/distro/include/yocto-uninative.inc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2021-03-08 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 16:47 Steve Sakoman [this message]
2021-03-08 16:47 ` [OE-core][dunfell 1/2] yocto-uninative.inc: version 2.11 updates glibc to 2.33 Steve Sakoman
2021-03-08 16:47 ` [OE-core][dunfell 2/2] yocto-uninative.inc: version 3.0 incorporate seccomp filter workaround Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2020-10-29 22:09 [OE-core][dunfell 0/2] Patch review Steve Sakoman
2020-10-05 22:57 Steve Sakoman
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=cover.1615221849.git.steve@sakoman.com \
--to=steve@sakoman.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox