From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: zhengruoqin <zhengrq.fnst@fujitsu.com>
Cc: meta-virtualization <meta-virtualization@yoctoproject.org>
Subject: Re: [meta-virtualization][PATCH] initrd: bump busybox to 1.33.1 to match oe-core
Date: Sun, 9 May 2021 23:04:59 -0400 [thread overview]
Message-ID: <CADkTA4PUxyb=FjZ9TLVMRMn5T_mMpuomAH-Pe0Psj9QEeqssLA@mail.gmail.com> (raw)
In-Reply-To: <1620615389-72870-1-git-send-email-zhengrq.fnst@fujitsu.com>
On Sun, May 9, 2021 at 10:56 PM zhengruoqin <zhengrq.fnst@fujitsu.com> wrote:
>
> OE core has updated busybox, so we bump to match.
>
Neither oe-core or poky master or master-next have 1.33.1 as the version yet.
I realize you just sent the upgrade to oe-core, but having already
sent this here, makes no sense.
I have tests that will pickup when it merges to master, and I'll bump
the version then. I'm dropping this for now, and will revisit when I
see the version land in master.
Cheers,
Bruce
> Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com>
> ---
> .../{busybox-initrd_1.33.0.bb => busybox-initrd_1.33.1.bb} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename recipes-core/busybox/{busybox-initrd_1.33.0.bb => busybox-initrd_1.33.1.bb} (100%)
>
> diff --git a/recipes-core/busybox/busybox-initrd_1.33.0.bb b/recipes-core/busybox/busybox-initrd_1.33.1.bb
> similarity index 100%
> rename from recipes-core/busybox/busybox-initrd_1.33.0.bb
> rename to recipes-core/busybox/busybox-initrd_1.33.1.bb
> --
> 2.25.1
>
>
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
next prev parent reply other threads:[~2021-05-10 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 2:56 [meta-virtualization][PATCH] initrd: bump busybox to 1.33.1 to match oe-core zhengruoqin
2021-05-10 3:04 ` Bruce Ashfield [this message]
2021-07-21 15:46 ` [PATCH] " Daniel Dragomir
2021-07-21 22:38 ` [meta-virtualization] " Bruce Ashfield
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='CADkTA4PUxyb=FjZ9TLVMRMn5T_mMpuomAH-Pe0Psj9QEeqssLA@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@yoctoproject.org \
--cc=zhengrq.fnst@fujitsu.com \
/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 NNTP newsgroup(s).