From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Alex Stewart <alex.stewart@ni.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][m-c-s][PATCH 0/3] Upgrade bbappends for nanbield compatibility
Date: Thu, 1 Feb 2024 14:20:01 +0000 [thread overview]
Message-ID: <ZbuokdlBvnCoPjvZ@gmail.com> (raw)
In-Reply-To: <20240126173050.1137474-1-alex.stewart@ni.com>
In message: [meta-virtualization][m-c-s][PATCH 0/3] Upgrade bbappends for nanbield compatibility
on 26/01/2024 Alex Stewart wrote:
> This patchset upgrades the bbappends of some recipes whose base versions
> have advanced in the main layers' nanbield releases.
Thanks for the updates. Most appreciated. I've just started updating
more parts of m-c-s and this helps me along with that effort.
Bruce
>
> Alex Stewart (3):
> qemu: upgrade bbappend to 8.%
> libvirt: upgrade bbappend to 9.%
> iproute2: upgrade bbappend to 6.%
>
> .../qemu/{qemu_7.%.bbappend => qemu_8.%.bbappend} | 0
> .../libvirt/{libvirt_8.%.bbappend => libvirt_9.%.bbappend} | 0
> .../iproute2/{iproute2_5.%.bbappend => iproute2_6.%.bbappend} | 0
> 3 files changed, 0 insertions(+), 0 deletions(-)
> rename meta-openstack/recipes-devtools/qemu/{qemu_7.%.bbappend => qemu_8.%.bbappend} (100%)
> rename meta-openstack/recipes-extended/libvirt/{libvirt_8.%.bbappend => libvirt_9.%.bbappend} (100%)
> rename meta-openstack/recipes-support/iproute2/{iproute2_5.%.bbappend => iproute2_6.%.bbappend} (100%)
>
> --
> 2.40.1
>
prev parent reply other threads:[~2024-02-01 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 17:30 [meta-virtualization][m-c-s][PATCH 0/3] Upgrade bbappends for nanbield compatibility Alex Stewart
2024-01-26 17:30 ` [meta-virtualization][m-c-s][PATCH 1/3] qemu: upgrade bbappend to 8.% Alex Stewart
2024-01-26 17:30 ` [meta-virtualization][m-c-s][PATCH 2/3] libvirt: upgrade bbappend to 9.% Alex Stewart
2024-01-26 17:30 ` [meta-virtualization][m-c-s][PATCH 3/3] iproute2: upgrade bbappend to 6.% Alex Stewart
2024-02-01 14:20 ` Bruce Ashfield [this message]
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=ZbuokdlBvnCoPjvZ@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=alex.stewart@ni.com \
--cc=meta-virtualization@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).