From: James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
To: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
Cc: CRIU <criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Serge Hallyn
<serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Subject: Re: [CRIU] CRIU @Plumbers
Date: Tue, 03 Feb 2015 07:52:50 -0800 [thread overview]
Message-ID: <1422978770.2090.2.camel@HansenPartnership.com> (raw)
In-Reply-To: <20150203154123.GB2923-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
On Tue, 2015-02-03 at 16:41 +0100, Serge E. Hallyn wrote:
> Quoting James Bottomley (James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org):
> > On Mon, 2015-02-02 at 16:58 +0000, Serge Hallyn wrote:
> > > I think it might be worthwhile - my main concern is that it not conflict
> > > timewise with the containers summit.
> >
> > You mean ContainerCon? That's running concurrently with LinuxCon, so it
> > shouldn't conflict with either of the two plumbers days.
>
> Sorry didn't mean "summit". I just mean the containers track at plumbers.
>
> http://wiki.linuxplumbersconf.org/2015:containers
Yes, Plumbers can take care of the scheduling. Since we have a Seattle
local team, we'll help running containers, which should make sure
there's no overlap ...
James
next prev parent reply other threads:[~2015-02-03 15:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 10:05 CRIU @Plumbers Pavel Emelyanov
[not found] ` <54CF4BFF.8070505-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2015-02-02 16:58 ` [CRIU] " Serge Hallyn
2015-02-03 3:50 ` James Bottomley
[not found] ` <1422935454.2103.48.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2015-02-03 15:41 ` Serge E. Hallyn
[not found] ` <20150203154123.GB2923-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2015-02-03 15:52 ` James Bottomley [this message]
2015-02-02 17:06 ` Tycho Andersen
2015-02-02 19:19 ` Saied Kazemi
[not found] ` <CA+Um-gj1ynTwOsQNV7482Lz2GsCX+Leuz=QdSfPL1MVaF1CRGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-03 14:58 ` Pavel Emelyanov
[not found] ` <54D0E216.3040007-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2015-02-03 16:10 ` Christopher Covington
[not found] ` <54D0F2EC.4040702-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-02-03 16:21 ` Saied Kazemi
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=1422978770.2090.2.camel@HansenPartnership.com \
--to=james.bottomley-d9phhud1jfjcxq6kfmz53/egyhegw8jk@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.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