From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Upcoming Buildroot Developer Days meeting
Date: Tue, 24 Jul 2012 09:34:17 +0200 [thread overview]
Message-ID: <20120724093417.1c81f9fd@skate> (raw)
Hello,
As discussed on the list in the past weeks, the next Buildroot
Developer Days meeting will take place on November 3-4 in Barcelona,
Spain, just before the Embedded Linux Conference Europe.
I have added an announcement of the meeting on
http://buildroot.org/news.html, I have closed the Doodle survey now
that the dates are decided, and I have created a section our wiki page
to collect:
* The list of participants, their arrival time, and hotel location
* The list of topics to discuss
See
http://elinux.org/Buildroot#Buildroot_Developers_Meeting.2C_3-4_November_2012.2C_Barcelona_Spain.
Please feel free to add yourself to the list of participants, add
your flight informations, or suggest topics to be discussed or worked
on.
Thanks for your participation,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
reply other threads:[~2012-07-24 7:34 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=20120724093417.1c81f9fd@skate \
--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