From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Sat, 9 Feb 2013 20:06:49 +0100 [thread overview]
Message-ID: <20130209200649.27b7e569@skate> (raw)
In-Reply-To: <20130209195709.323b9f5e@skate>
On Sat, 9 Feb 2013 19:57:09 +0100, Thomas Petazzoni wrote:
> As I am going to the Embedded Linux Conference in San Francisco, I've
> submitted a proposal to have a booth at the technical showcase to
> demonstrate Buildroot. The technical showcase takes place after the
> conferences, during about 1 hour, on one evening of the event. My
> proposal has been accepted. It's a good opportunity to raise the
> attention around Buildroot to the ELC crowd.
For more details about the showcase, see
http://www.elinux.org/ELC_2013_Technical_Showcase.
> Therefore, I am requesting your help to:
>
> * Review the Buildroot poster I've made. The poster will be printed by
> the event organizers in big format, and I've tried to highlight the
> main fact about Buildroot, and recent developments.
>
> See http://free-electrons.com/~thomas/pub/buildroot-poster.png
One thing I could have mentioned is that the project is
"Vendor-neutral". I.e, not backed by a single big company, but really
driven by an open community. Not sure if this is important enough to be
mentioned on this poster (considering the limited paper space, we have
to chose what are the main informations we want to show).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-09 19:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 18:57 [Buildroot] Buildroot at ELC: review/suggestions needed Thomas Petazzoni
2013-02-09 19:06 ` Thomas Petazzoni [this message]
2013-02-09 23:47 ` Yann E. MORIN
2013-02-10 9:50 ` Peter Korsgaard
2013-02-10 10:59 ` Yann E. MORIN
2013-02-11 8:24 ` Thomas Petazzoni
2013-02-11 9:51 ` Will Newton
2013-02-11 10:31 ` Thomas Petazzoni
2013-02-11 17:34 ` Luca Ceresoli
2013-02-10 11:28 ` Stephan Hoffmann
2013-02-11 8:26 ` Thomas Petazzoni
2013-02-10 12:46 ` Belisko Marek
2013-02-11 8:42 ` Thomas Petazzoni
2013-02-11 8:33 ` Yegor Yefremov
2013-02-11 13:38 ` Shawn J. Goff
2013-02-24 4:07 ` Thomas Petazzoni
2013-02-13 22:13 ` Thomas Petazzoni
2013-02-13 22:57 ` Yann E. MORIN
2013-02-13 23:13 ` Arnout Vandecappelle
2013-02-14 5:35 ` Baruch Siach
2013-02-14 9:46 ` Thomas Petazzoni
2013-02-14 9:54 ` Jeremy Rosen
2013-02-14 9:58 ` Thomas Petazzoni
2013-02-14 12:34 ` Baruch Siach
2013-02-14 9:53 ` Will Moore
2013-02-14 10:05 ` Thomas Petazzoni
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=20130209200649.27b7e569@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