From: "Adam Johnston" <adam.johnston@arm.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: Re: [PATCH] docker: update from 24.0.2 to 24.0.5
Date: Thu, 21 Sep 2023 07:16:46 -0700 [thread overview]
Message-ID: <10621.1695305806905466193@lists.yoctoproject.org> (raw)
In-Reply-To: <558.1695305548586655871@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 109 bytes --]
Bad assumption. I see docker-moby has already bumped to 24.x.x
We will create a patch
Regards
Adam
[-- Attachment #2: Type: text/html, Size: 133 bytes --]
next prev parent reply other threads:[~2023-09-21 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 8:22 [meta-virtualization][PATCH] docker: update from 24.0.2 to 24.0.5 mikko.rapeli
2023-08-02 13:12 ` Bruce Ashfield
2023-08-14 6:10 ` Mikko Rapeli
2023-08-14 12:44 ` Martin Jansa
2023-08-14 12:59 ` Mikko Rapeli
2023-09-21 11:20 ` [PATCH] " Adam Johnston
2023-09-21 13:07 ` [meta-virtualization] " Mikko Rapeli
2023-09-21 14:12 ` Adam Johnston
2023-09-21 14:12 ` Adam Johnston
2023-09-21 14:16 ` Adam Johnston [this message]
2023-08-14 13:09 ` [meta-virtualization][PATCH] " Bruce Ashfield
2023-08-14 13:12 ` Martin Jansa
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=10621.1695305806905466193@lists.yoctoproject.org \
--to=adam.johnston@arm.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).