From: Steve Sakoman <steve@sakoman.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][dunfell 0/8] Pull request (cover letter only)
Date: Wed, 4 May 2022 12:59:44 -1000 [thread overview]
Message-ID: <cover.1651705136.git.steve@sakoman.com> (raw)
The following changes since commit bb3fc61f0d7f7bcd77ef194b76f4fdd8a7ff6aa5:
scripts/contrib/oe-build-perf-report-email.py: remove obsolete check for phantomjs and optipng (2022-04-27 05:00:00 -1000)
are available in the Git repository at:
git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-next
Chen Qi (1):
cases/buildepoxy.py: fix typo
Khem Raj (1):
busybox: Use base_bindir instead of hardcoding /bin path
Paul Gortmaker (1):
install/devshell: Introduce git intercept script due to fakeroot
issues
Rahul Kumar (1):
neard: Switch SRC_URI to git repo
Richard Purdie (2):
base: Drop git intercept
uninative: Upgrade to 3.6 with gcc 12 support
Ross Burton (2):
python3: ignore CVE-2015-20107
bitbake.conf: mark all directories as safe for git to read
meta/classes/devshell.bbclass | 2 ++
meta/conf/bitbake.conf | 8 ++++++++
meta/conf/distro/include/yocto-uninative.inc | 8 ++++----
meta/lib/oeqa/sdk/cases/buildepoxy.py | 2 +-
meta/recipes-connectivity/neard/neard_0.16.bb | 13 +++++++------
meta/recipes-core/busybox/busybox.inc | 2 +-
.../recipes-devtools/python/python3_3.8.13.bb | 3 +++
scripts/git-intercept/git | 19 +++++++++++++++++++
8 files changed, 45 insertions(+), 12 deletions(-)
create mode 100755 scripts/git-intercept/git
--
2.25.1
next reply other threads:[~2022-05-04 23:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 22:59 Steve Sakoman [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 14:40 [OE-core][dunfell 0/8] Pull request (cover letter only) Steve Sakoman
2022-11-09 2:24 Steve Sakoman
2022-04-06 16:37 Steve Sakoman
2020-05-14 15:40 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.1651705136.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.