From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: ckrm-tech-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
pj-sJ/iWh9BUns@public.gmane.org,
Rohit Seth <rohitseth-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
cpw-sJ/iWh9BUns@public.gmane.org,
"Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
Subject: Re: [Devel] containers development plans
Date: Mon, 23 Jul 2007 15:40:06 +0200 [thread overview]
Message-ID: <46A4AFB6.9070302@fr.ibm.com> (raw)
In-Reply-To: <20070717181002.GB9383-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
Serge E. Hallyn wrote:
> Quoting Kirill Korotaev (dev-3ImXcnM4P+0@public.gmane.org):
>>> Unfortunately I'm unlikely to be there (late notice - I really need to
>>> keep a better list of upcoming conferences and proposal deadlines!).
>>> But it still sounds like a good idea.
>> It's a pity :/ I though you are the primary candidate for presenting containers at KLS.
>
> I would be able to get approval to attend KS. I just wouldn't be able to
> get approval to attend the linuxconf europe without presenting a paper,
> which it is too late to do.
>
> So if I happen to go to KS, I can attend the miniconf. If not, then:
when is the mini conf planned ? the 3rd of September, just before KS ?
thanks,
C.
next prev parent reply other threads:[~2007-07-23 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070702165504.GA18075@vino.hallyn.com>
[not found] ` <46984121.8070301@openvz.org>
[not found] ` <20070714201537.GC22931@vino.hallyn.com>
[not found] ` <20070714201537.GC22931-4+H9nbzk0uAIagZqoN9o3w@public.gmane.org>
2007-07-14 23:28 ` [Devel] containers development plans Kir Kolyshkin
[not found] ` <46984121.8070301-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-07-16 23:08 ` Rohit Seth
[not found] ` <1184627311.10091.252.camel-7OsMPKyG+FJSzHKm+aFRNNkmqwFzkYv6@public.gmane.org>
2007-07-17 10:17 ` Serge E. Hallyn
[not found] ` <20070717101712.GB6101-4+H9nbzk0uAIagZqoN9o3w@public.gmane.org>
2007-07-17 13:51 ` Kirill Korotaev
[not found] ` <469CC969.9080103-3ImXcnM4P+0@public.gmane.org>
2007-07-17 18:10 ` Serge E. Hallyn
[not found] ` <20070717181002.GB9383-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-07-23 13:40 ` Cedric Le Goater [this message]
[not found] ` <46A4AFB6.9070302-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-07-23 14:10 ` Serge E. Hallyn
[not found] ` <20070723141000.GA30590-4+H9nbzk0uAIagZqoN9o3w@public.gmane.org>
2007-07-23 14:54 ` [ckrm-tech] " Paul Menage
2007-07-17 16:19 ` Paul (宝瑠) Menage
[not found] ` <6599ad830707170919s33974d76o5bb553e680de9010-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-17 18:11 ` Serge E. Hallyn
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=46A4AFB6.9070302@fr.ibm.com \
--to=clg-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=ckrm-tech-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=cpw-sJ/iWh9BUns@public.gmane.org \
--cc=pj-sJ/iWh9BUns@public.gmane.org \
--cc=rohitseth-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+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 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.