From: "Serge E. Hallyn" <serge@hallyn.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Tycho Andersen" <tycho.andersen@canonical.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Christian Brauner" <christian.brauner@mailbox.org>,
"James Bottomley" <James.Bottomley@HansenPartnership.com>,
"Stéphane Graber" <stgraber@ubuntu.com>
Subject: Re: [Ksummit-discuss] [LAST-MINUTE TOPIC] cgroup API
Date: Mon, 31 Oct 2016 12:40:05 -0500 [thread overview]
Message-ID: <20161031174005.GA9473@mail.hallyn.com> (raw)
In-Reply-To: <20161031173351.GA28466@mtj.duckdns.org>
Quoting Tejun Heo (tj@kernel.org):
> Hello,
>
> On Mon, Oct 31, 2016 at 01:06:00PM -0400, Theodore Ts'o wrote:
> > On Mon, Oct 31, 2016 at 09:19:59AM -0600, Tejun Heo wrote:
> > >
> > > Sorry, wasn't looking at emails yesteray. Yeah, early Tue afternoon
> > > works for me as long as we can finish before 4pm.
> >
> > Does 3pm work for everyone? Or would you like to do something a bit
> > earlier on Tuesday afternoon? Say, 2m?
>
> I think 2pm would be better but 3pm works fine too. How about
> everyone else?
Both work for me. Sounds like 2pm is the safer bet if noone has
a conflict.
next prev parent reply other threads:[~2016-10-31 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 17:29 [Ksummit-discuss] [LAST-MINUTE TOPIC] cgroup API Andy Lutomirski
2016-10-27 17:39 ` James Bottomley
2016-10-27 17:45 ` Josh Triplett
2016-10-27 20:09 ` Tejun Heo
2016-10-27 20:11 ` Paul Turner
2016-10-27 21:13 ` Peter Zijlstra
2016-10-30 23:50 ` Theodore Ts'o
2016-10-31 17:41 ` Rik van Riel
2016-10-30 15:27 ` Serge E. Hallyn
2016-10-30 23:41 ` Theodore Ts'o
2016-10-31 3:39 ` James Bottomley
2016-10-31 15:04 ` Serge E. Hallyn
2016-10-31 15:19 ` Tejun Heo
2016-10-31 17:06 ` Theodore Ts'o
2016-10-31 17:33 ` Tejun Heo
2016-10-31 17:35 ` James Bottomley
2016-11-01 13:33 ` James Bottomley
2016-10-31 17:40 ` Serge E. Hallyn [this message]
2016-10-31 17:42 ` Stéphane Graber
2016-10-31 23:00 ` Christian Brauner
2016-10-31 15:28 ` James Bottomley
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=20161031174005.GA9473@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=christian.brauner@mailbox.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=peterz@infradead.org \
--cc=stgraber@ubuntu.com \
--cc=tj@kernel.org \
--cc=tycho.andersen@canonical.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.