From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot meeting at FOSDEM: reminder
Date: Mon, 18 Jan 2016 16:09:26 +0100 [thread overview]
Message-ID: <20160118160926.659219c1@free-electrons.com> (raw)
Hello,
This is an e-mail to remind everyone about the Buildroot Developers
Meeting that will take place right after FOSDEM in Brussels, on
February 1-2. We have a Wiki page about this event:
http://elinux.org/Buildroot:DeveloperDaysFOSDEM2016
Eleven participants have already registered. If you are a Buildroot
developer and want to attend, please let us know, it is not too late to
register (participation is free).
Also, whether you will participate physically to the event or not, you
are very much encouraged to suggest some topics that should be
discussed. If you cannot attend, we can arrange some remote discussion
(via IRC or Google Hangout) during the meeting. A significant number of
core Buildroot developers will be at the meeting, so it is the perfect
time to take some decisions on specific technical topics.
Thanks for your participation,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
reply other threads:[~2016-01-18 15:09 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=20160118160926.659219c1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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