Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn J. Goff <shawn.goff@accelecon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Mon, 11 Feb 2013 08:38:15 -0500	[thread overview]
Message-ID: <kfas86$h71$1@ger.gmane.org> (raw)
In-Reply-To: <20130209195709.323b9f5e@skate>

On 02/09/2013 01:57 PM, Thomas Petazzoni wrote:
> Hello,
>
> 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.
>
> 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
>
>   * Give me suggestions on what to demonstrate. I will prepare a
>     slideshow of 10-20 slides that continuously loops (it should
>     present the main characteristics and features of Buildroot), but I
>     also would like to have some demo to show (I can bring an ARM board
>     if needed). Any suggestions, both for the slideshow and the demo?
>
> Thanks for your help,
>
> Thomas
>

If you want to take this opportunity to try out the Vector logo I worked 
on previously, it was made in Inkscape, so it should be as simple as 
copy+paste the one that you like.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot_logo.svg
Type: image/svg+xml
Size: 89625 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130211/c6ae3774/attachment-0001.svg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: buildroot_logo.png
Type: image/png
Size: 186402 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130211/c6ae3774/attachment-0001.png>

  parent reply	other threads:[~2013-02-11 13:38 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
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 [this message]
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='kfas86$h71$1@ger.gmane.org' \
    --to=shawn.goff@accelecon.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