From: Denys Dmytriyenko <denis@denix.org>
To: m.cavallini@koansoftware.com,
openembedded-members@lists.openembedded.org
Cc: Yocto Project <yocto@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: OEDEM in Edinburgh in 2 weeks
Date: Fri, 5 Oct 2018 11:22:56 -0400 [thread overview]
Message-ID: <20181005152256.GI7186@denix.org> (raw)
In-Reply-To: <75ed6afa-3a4a-e6ea-83d2-b65928a575da@koansoftware.com>
On Thu, Oct 04, 2018 at 02:42:41PM +0200, Marco Cavallini wrote:
> Il 04/10/2018 14:20, Philip Balister ha scritto:
> >OEDEM is basically full at this time.
> >
> >https://www.openembedded.org/wiki/OEDEM_2018
> >
> >We have had the room rearranged to seat 45 people and I am not sure how
> >we would handle anyone over this. If you know you can't make it, could
> >you please remove your name from the attendee list. We'd like to get a
> >better idea of how many people on the waiting list we can accommodate.
> >There are some long time contributors on the wait list we'd like to get in.
> >
> >Philip
> >
>
>
> Hi Philip,
> if I can participate remaining standing, will be a pleasure to leave
> my seat to one of the long time contributors on the wait list ;-)
Marco,
Unfortunately, I don't believe those are seating vs. standing spaces, but
rather the maximum number of people allowed in the root at the same time,
limited by a fire marshal for safety...
--
Denys
next prev parent reply other threads:[~2018-10-05 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 12:20 OEDEM in Edinburgh in 2 weeks Philip Balister
2018-10-04 12:42 ` Marco Cavallini
2018-10-05 15:22 ` Denys Dmytriyenko [this message]
2018-10-10 13:56 ` [yocto] " Philip Balister
2018-10-10 13:56 ` Philip Balister
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=20181005152256.GI7186@denix.org \
--to=denis@denix.org \
--cc=m.cavallini@koansoftware.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-members@lists.openembedded.org \
--cc=yocto@yoctoproject.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.