From: Aleksa Sarai <asarai@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
Linux Containers <containers@lists.linux-foundation.org>,
overlayfs <linux-unionfs@vger.kernel.org>
Subject: Re: Overlayfs @Plumbers
Date: Sat, 29 Aug 2020 01:58:49 +1000 [thread overview]
Message-ID: <20200828155849.k46uk3x63aio3g3o@yavin.dot.cyphar.com> (raw)
In-Reply-To: <87tuwmiy4j.fsf@x220.int.ebiederm.org>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
On 2020-08-28, Eric W. Biederman <ebiederm@xmission.com> wrote:
> Amir Goldstein <amir73il@gmail.com> writes:
>
> > Hi Guys,
> >
> > It's been nice to virtually meet with you yesterday.
> > Some of you wanted to follow up on overlayfs related issues.
> >
> > If you want to discuss, try to find me in one of the
> > https://meet.2020.linuxplumbersconf.org/hackrooms
> > today between 16:00-17:00 UTC
> > (No need to enter the room to see who's inside)
> >
> > If those times do not work for you, contact me and we can try
> > to schedule another time.
>
> Did this conversation wind up happening? Do we need to reschedule?
This conversation already happened in a Hackroom on Tuesday. I'm not
sure if the Hackrooms will have their recordings published, so maybe
Amir can post any of the takeaways we had?
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
<https://www.cyphar.com/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-28 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 6:07 Overlayfs @Plumbers Amir Goldstein
2020-08-28 15:33 ` Eric W. Biederman
2020-08-28 15:58 ` Aleksa Sarai [this message]
2020-08-29 15:40 ` Sargun Dhillon
2020-08-30 11:29 ` Giuseppe Scrivano
2020-08-30 11:37 ` Amir Goldstein
2020-08-30 11:44 ` Amir Goldstein
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=20200828155849.k46uk3x63aio3g3o@yavin.dot.cyphar.com \
--to=asarai@suse.de \
--cc=amir73il@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-unionfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).