From: <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] meta: Upgrade gettext and nfs-utils
Date: Mon, 4 Dec 2023 22:44:08 -0800 [thread overview]
Message-ID: <cover.1701758555.git.liezhi.yang@windriver.com> (raw)
From: Robert Yang <liezhi.yang@windriver.com>
The following changes since commit d2c4e8cb85c6a5ca37c7990f879c3b650df5770b:
vte: Separate out gtk4 pieces of vte into individual packages (2023-12-04 12:45:20 +0000)
are available in the Git repository at:
https://github.com/robertlinux/yocto rbt/upgrade
https://github.com/robertlinux/yocto/tree/rbt/upgrade
Robert Yang (2):
gettext: Upgrade 0.22.3 -> 0.22.4
nfs-utils: Upgrade 2.6.3 -> 2.6.4
...event-and-libsqlite3-checked-when-nf.patch | 80 -------------------
...{nfs-utils_2.6.3.bb => nfs-utils_2.6.4.bb} | 3 +-
....3.bb => gettext-minimal-native_0.22.4.bb} | 0
meta/recipes-core/gettext/gettext-sources.inc | 2 +-
.../{gettext_0.22.3.bb => gettext_0.22.4.bb} | 0
5 files changed, 2 insertions(+), 83 deletions(-)
delete mode 100644 meta/recipes-connectivity/nfs-utils/nfs-utils/0001-configure.ac-libevent-and-libsqlite3-checked-when-nf.patch
rename meta/recipes-connectivity/nfs-utils/{nfs-utils_2.6.3.bb => nfs-utils_2.6.4.bb} (97%)
rename meta/recipes-core/gettext/{gettext-minimal-native_0.22.3.bb => gettext-minimal-native_0.22.4.bb} (100%)
rename meta/recipes-core/gettext/{gettext_0.22.3.bb => gettext_0.22.4.bb} (100%)
--
2.42.0
next reply other threads:[~2023-12-05 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 6:44 liezhi.yang [this message]
2023-12-05 6:44 ` [PATCH 1/2] gettext: Upgrade 0.22.3 -> 0.22.4 liezhi.yang
2023-12-05 6:44 ` [PATCH 2/2] nfs-utils: Upgrade 2.6.3 -> 2.6.4 liezhi.yang
2023-12-05 16:15 ` [OE-core] " Alexandre Belloni
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.1701758555.git.liezhi.yang@windriver.com \
--to=liezhi.yang@windriver.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.