From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/3] Patch review
Date: Tue, 8 Mar 2022 04:13:29 -1000 [thread overview]
Message-ID: <cover.1646748150.git.steve@sakoman.com> (raw)
Please review this set of patches for dunfell and have comments back by
end of day Thursday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3335
The following changes since commit 51844f2d60d77fb8cb46ffe460402f76ae216ca5:
uninative: Upgrade to 3.5 (2022-03-03 07:43:07 -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
Jose Quaresma (1):
sstate: inside the threadedpool don't write to the shared localdata
Richard Purdie (1):
systemd: Ensure uid/gid ranges are set deterministically
Ross Burton (1):
asciidoc: update git repository
meta/classes/sstate.bbclass | 2 +-
meta/recipes-core/systemd/systemd_244.5.bb | 2 ++
meta/recipes-extended/asciidoc/asciidoc_8.6.9.bb | 2 +-
3 files changed, 4 insertions(+), 2 deletions(-)
--
2.25.1
next reply other threads:[~2022-03-08 14:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 14:13 Steve Sakoman [this message]
2022-03-08 14:13 ` [OE-core][dunfell 1/3] asciidoc: update git repository Steve Sakoman
2022-03-08 14:13 ` [OE-core][dunfell 2/3] systemd: Ensure uid/gid ranges are set deterministically Steve Sakoman
2022-03-08 14:13 ` [OE-core][dunfell 3/3] sstate: inside the threadedpool don't write to the shared localdata Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2024-01-03 3:13 [OE-core][dunfell 0/3] Patch review Steve Sakoman
2022-09-29 2:05 Steve Sakoman
2022-07-13 19:46 Steve Sakoman
2022-03-10 14:04 Steve Sakoman
2021-11-04 14:06 Steve Sakoman
2021-07-20 21:57 Steve Sakoman
2021-05-21 0:19 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.1646748150.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 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.