From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Stéphane Graber" <stgraber@ubuntu.com>,
lxc-devel@lists.linuxcontainers.org,
lxc-users@lists.linuxcontainers.org,
containers@lists.linuxfoundation.org,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Containers and checkpoint/restart micro-conference at LPC2018
Date: Sun, 09 Sep 2018 08:30:39 -0700 [thread overview]
Message-ID: <1536507039.3192.5.camel@HansenPartnership.com> (raw)
In-Reply-To: <20180813161015.GD18492@castiana>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Mon, 2018-08-13 at 12:10 -0400, Stéphane Graber wrote:
> Details can be found here:
>
> https://discuss.linuxcontainers.org/t/containers-micro-conference-a
> t-linux-plumbers-2018/2417
This website was giving a 503 error when I looked.
However, if you want a discussion on the requirements for shiftfs (and
whether we still need it), I'm up for that.
James
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-09-09 20:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:10 Containers and checkpoint/restart micro-conference at LPC2018 Stéphane Graber
2018-09-08 4:59 ` Stéphane Graber
2018-09-08 4:59 ` Stéphane Graber
2018-09-08 7:41 ` Amir Goldstein
2018-09-08 7:41 ` Amir Goldstein
2018-09-09 1:31 ` Christian Brauner
2018-09-09 6:31 ` Overlayfs @ " Amir Goldstein
2018-09-09 6:31 ` Amir Goldstein
2018-09-09 9:18 ` Christian Brauner
2018-09-11 13:52 ` Vivek Goyal
2018-09-11 13:52 ` Vivek Goyal
2018-09-11 15:13 ` James Bottomley
2018-09-11 15:13 ` James Bottomley
2018-09-11 15:36 ` Vivek Goyal
2018-09-11 15:36 ` Vivek Goyal
2018-09-09 19:08 ` [lxc-users] " Lucas Oketch
2018-09-09 15:30 ` James Bottomley [this message]
2018-09-09 17:38 ` Steve French
2018-09-09 17:38 ` Steve French
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=1536507039.3192.5.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=containers@lists.linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lxc-devel@lists.linuxcontainers.org \
--cc=lxc-users@lists.linuxcontainers.org \
--cc=netdev@vger.kernel.org \
--cc=stgraber@ubuntu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.