From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Poll for Buildroot Meeting @ ELCE
Date: Wed, 13 Jun 2018 10:19:30 +0200 [thread overview]
Message-ID: <20180613101930.5a8601cf@windsurf> (raw)
Hello,
The next Buildroot Developers Meeting will take place next to the
Embedded Linux Conference Europe in Edinburgh.
ELCE itself is help from October 22 (Monday) to October 24 (Wednesday).
The question is whether we should have the Buildroot meeting before
ELCE (on Saturday/Sunday) or after ELCE (Thursday/Friday).
We traditionally had the meeting before ELCE, on Saturday/Sunday, so
that people who are not paid by their employer to attend the meeting
can do so without having to take vacations. It also allows to avoid
conflicting with other potential co-located events to ELCE that
typically take place on Thursday after the conference.
But in order to decide, I've opened a poll at:
https://framadate.org/Jd9UWGQVre9ctB42
If you intend to participate to this meeting, please fill in this poll,
so that we can chose the option that suits the highest number of
potential participants.
Thanks!
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
reply other threads:[~2018-06-13 8:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180613101930.5a8601cf@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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