From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH 1/1] package/containerd: security bump to v2.0.7
Date: Wed, 25 Feb 2026 22:10:22 +0100 [thread overview]
Message-ID: <8e32328df393792f01b394205c3428b8@free.fr> (raw)
In-Reply-To: <20260225094824.270893-1-thomas.perale@mind.be>
On 25/02/2026 10:48, Thomas Perale via buildroot wrote:
> For more information on the version bump, see:
> - https://github.com/containerd/containerd/releases/tag/v2.0.7
> - https://github.com/containerd/containerd/releases/tag/v2.0.6
> - https://github.com/containerd/containerd/releases/tag/v2.0.5
> - https://github.com/containerd/containerd/releases/tag/v2.0.4
> - https://github.com/containerd/containerd/releases/tag/v2.0.3
[...]
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-02-25 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 9:48 [Buildroot] [PATCH 1/1] package/containerd: security bump to v2.0.7 Thomas Perale via buildroot
2026-02-25 9:48 ` [Buildroot] [PATCH] package/wireshark: security bump to v4.4.13 Thomas Perale via buildroot
2026-02-25 9:57 ` Thomas Perale via buildroot
2026-02-25 21:10 ` Julien Olivain via buildroot [this message]
2026-03-06 19:53 ` [Buildroot] [PATCH 1/1] package/containerd: security bump to v2.0.7 Thomas Perale via buildroot
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=8e32328df393792f01b394205c3428b8@free.fr \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=ju.o@free.fr \
--cc=thomas.perale@mind.be \
/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