All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
To: "Stéphane Graber" <stgraber-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: LXC users mailing-list
	<lxc-users-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org>,
	containers-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.org,
	LXC development mailing-list
	<lxc-devel-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org>,
	brandon-Qdl1sq8EXS0@public.gmane.org
Subject: Re: [lxc-users] [lxc-devel] Schedule for the Containers mini-summit at LPC 2014 (next week in Düsseldorf)
Date: Fri, 10 Oct 2014 16:01:43 -0700	[thread overview]
Message-ID: <1412982103.2068.24.camel@jarvis.lan> (raw)
In-Reply-To: <20141010155334.GE24284@castiana>

On Fri, 2014-10-10 at 17:53 +0200, Stéphane Graber wrote:
> I don't remember seeing a clear yes or no on that question but last
> year's edition was so I'm hopeful.

Actually, no.  The demand for recording the conferences this year was
about treble the estimate (due to staffing levels required by the
unions, I think), so we just couldn't afford it.

James


_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

      reply	other threads:[~2014-10-10 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 15:21 Schedule for the Containers mini-summit at LPC 2014 (next week in Düsseldorf) Stéphane Graber
2014-10-10 15:38 ` [lxc-devel] " Michael H. Warfield
     [not found] ` <1412955510.26860.197.camel@canyon.ip6.wittsend.com>
     [not found]   ` <1412955510.26860.197.camel-vOfUpqNauDHtTQEGl6Np2G/jKlrYuGwS@public.gmane.org>
2014-10-10 15:53     ` [lxc-users] " Stéphane Graber
2014-10-10 23:01       ` James Bottomley [this message]

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=1412982103.2068.24.camel@jarvis.lan \
    --to=james.bottomley-d9phhud1jfjcxq6kfmz53/egyhegw8jk@public.gmane.org \
    --cc=brandon-Qdl1sq8EXS0@public.gmane.org \
    --cc=containers-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.org \
    --cc=lxc-devel-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org \
    --cc=lxc-users-cunTk1MwBs9qMoObBWhMNEqPaTDuhLve2LY78lusg7I@public.gmane.org \
    --cc=stgraber-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 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.