From: Christian Stewart <christian@paral.in>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7] Bump docker packages to v18.09.4
Date: Sun, 07 Apr 2019 21:35:24 -0700 [thread overview]
Message-ID: <87ef6df71v.fsf@paral.in> (raw)
In-Reply-To: <87k1g6jh9i.fsf@dell.be.48ers.dk>
Hi Peter,
Peter Korsgaard <peter@korsgaard.com> writes:
> > I ran into some unrelated issues and was delayed a bit on this. I'm
> > compiling the images now and will try to get the testing done within 24
> > hours.
>
> Ok, thanks.
Looks good from initial tests. I see it's been merged as well.
Best regards,
Christian
next prev parent reply other threads:[~2019-04-08 4:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 18:23 [Buildroot] [PATCH 0/7] Bump docker packages to v18.09.4 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 1/7] package/runc: bump to version 1.0.0-rc7 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 2/7] Revert "package/runc: blacklist Codesourcery ARM toolchain" Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 3/7] Revert "runc: depend on linux headers >= 3.11 for O_TMPFILE" Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 4/7] package/docker-containerd: bump version to v1.2.5 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 5/7] package/docker-containerd: refer to official website Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 6/7] package/docker-engine: bump to version v18.09.4 Peter Korsgaard
2019-04-01 18:23 ` [Buildroot] [PATCH 7/7] package/docker-cli: " Peter Korsgaard
[not found] ` <87mul8vgj8.fsf@paral.in>
2019-04-02 15:24 ` [Buildroot] [PATCH 0/7] Bump docker packages to v18.09.4 Peter Korsgaard
2019-04-07 7:20 ` Peter Korsgaard
2019-04-07 8:56 ` Christian Stewart
2019-04-07 9:28 ` Peter Korsgaard
2019-04-08 4:35 ` Christian Stewart [this message]
2019-04-08 6:12 ` Peter Korsgaard
2019-04-14 21:15 ` Peter Korsgaard
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=87ef6df71v.fsf@paral.in \
--to=christian@paral.in \
--cc=buildroot@busybox.net \
/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