From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v6 1/5] runc: new package
Date: Mon, 4 Jul 2016 23:17:39 +0200 [thread overview]
Message-ID: <a7de91c6-55ed-6592-0eb2-32941df7195f@gmail.com> (raw)
In-Reply-To: <1467662962069-86a12333-f03da0ee-0d3ff579@mixmax.com>
Le 04/07/2016 ? 22:09, Christian Stewart a ?crit :
> Romain,
>
> On Mon, Jul 4, 2016 1:05 PM, Romain Naour romain.naour at gmail.com
> <mailto:romain.naour@gmail.com> wrote:
>
> Usually we prefer a stable release but ok for this new package.
>
>
> Unfortunately they haven't spun a release in ages and Docker is using a commit
> pin as well. It's a bit of a weird setup they have going.
>
> I have it pinned to a newer release because some aarch64 fixes are in there.
I asked to Thomas about using -rc version and he say that it's fine for a new
package and to avoid carrying to much patches in Buildroot.
Best regards,
Romain
>
> Best,
> Christian
>
prev parent reply other threads:[~2016-07-04 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 19:26 [Buildroot] [PATCH v6 1/5] runc: new package Christian Stewart
2016-07-04 19:26 ` [Buildroot] [PATCH v6 2/5] docker-containerd: " Christian Stewart
2016-07-04 20:13 ` Romain Naour
2016-07-04 20:15 ` Christian Stewart
2016-07-04 19:26 ` [Buildroot] [PATCH v6 3/5] docker-engine: " Christian Stewart
2016-07-04 20:27 ` Romain Naour
2016-07-04 21:25 ` Romain Naour
2016-07-04 19:26 ` [Buildroot] [PATCH v6 4/5] package/docker-engine: proper sysv init file Christian Stewart
2016-07-04 19:28 ` Christian Stewart
2016-07-04 19:33 ` Thomas Petazzoni
2016-07-04 21:12 ` Romain Naour
2016-07-04 19:26 ` [Buildroot] [PATCH v6 5/5] package/docker-engine: restart - switch from ps -p to searching proc Christian Stewart
2016-07-04 20:05 ` [Buildroot] [PATCH v6 1/5] runc: new package Romain Naour
2016-07-04 20:09 ` Christian Stewart
2016-07-04 21:17 ` Romain Naour [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=a7de91c6-55ed-6592-0eb2-32941df7195f@gmail.com \
--to=romain.naour@gmail.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