From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developers Meeting @ ELCE 2018: reminder
Date: Wed, 29 Aug 2018 15:21:25 +0200 [thread overview]
Message-ID: <20180829152125.7f5d0ba1@windsurf> (raw)
Hello,
This is a reminder that the next Buildroot Developers Meeting will take
place on October 20-21 in Edinburgh (UK), right before ELCE.
At this time, we have six participants registered:
https://elinux.org/Buildroot:DeveloperDaysELCE2018. Since we are trying
to organize a meeting room, we would like to know if the number of
participants will remain about the same, or if there are other people
that are still considering attending the meeting, but have not yet
registered.
I know that both Romain Naour and Yann E. Morin may be attending but
are not yet sure at this point. Are there other people in this
situation ? Or are there others who know they will be attending, but
simply overlooked to register ?
Thanks a lot for your participation!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
reply other threads:[~2018-08-29 13:21 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=20180829152125.7f5d0ba1@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