From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] runc: bump to version 9df8b306d01f59d3a8029be411de015b7304dd8f
Date: Mon, 27 Feb 2017 13:20:49 +0100 [thread overview]
Message-ID: <20170227132049.52bc154c@free-electrons.com> (raw)
In-Reply-To: <CA+h8R2pTCALHiS5gtDUH-SLYFb7pCdZaguM7TEhM0WTW6CFh4Q@mail.gmail.com>
Hello,
On Fri, 24 Feb 2017 17:24:27 -0500, Christian Stewart wrote:
> It's a shame we have to commit-pin docker-containerd, but it seems
> necessary as they haven't cut another release yet.
>
> Patch 3/3 looks fine to me. I can't compile-test at the moment - I will be
> able to Monday, but I'm willing to bet you've got that covered already. I
> examined the changes to Docker in this release and they have changed the
> structure of their vendor tree a bit, making the changes in patch 3
> necessary.
Thanks, so I've committed Fabrice patches.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-02-27 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 15:46 [Buildroot] [PATCH 1/3] runc: bump to version 9df8b306d01f59d3a8029be411de015b7304dd8f Fabrice Fontaine
2017-02-22 15:46 ` [Buildroot] [PATCH 2/3] docker-containerd: bump to version aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1 Fabrice Fontaine
2017-02-22 15:46 ` [Buildroot] [PATCH 3/3] docker-engine: bump to version 1.13.1 Fabrice Fontaine
2017-02-23 21:34 ` [Buildroot] [PATCH 1/3] runc: bump to version 9df8b306d01f59d3a8029be411de015b7304dd8f Thomas Petazzoni
2017-02-24 22:24 ` Christian Stewart
2017-02-27 12:20 ` Thomas Petazzoni [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=20170227132049.52bc154c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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