From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Thu, 14 Feb 2013 11:05:36 +0100 [thread overview]
Message-ID: <20130214110536.37d54d34@skate> (raw)
In-Reply-To: <63C31970879140E7839D65DDAADF4076@beraninstruments.com.local>
Dear Will Moore,
On Thu, 14 Feb 2013 09:53:38 -0000, Will Moore wrote:
> > The current state of the slides is visible at
> > http://free-electrons.com/~thomas/pub/buildroot-slides.pdf.
> >
> > The two slides about build time and system size are still empty, I'm
> > currently making the experiments to get the numbers.
>
> Looks good, some small suggestions that might improve them:
>
> Slide 3/11 replace "product makers" with "product manufacturers"?
> Slide 6/11 replace "Allows to significantly improve Buildroot
> quality, by" with "Allows significant improvement of Buildroot
> quality by"? Slide 7/11 I appreciate this is a list of packages but
> is it clear that Buildroot can build you a toolchain? I might also
> expect to see bootloaders, Linux, busybox earlier in the list as the
> starting point of almost all Buildroot usage with the more important
> packages later in the list, but I appreciate what is "important" is
> personal... Slide 8/11 replace "weights about" with "weighs in at
> approximately". Slide 11/11 it might be better to show a more
> interesting page of the user manual.
Thanks, slides updated to take into account your comments!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-02-14 10:05 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
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 [this message]
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=20130214110536.37d54d34@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