All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Mon, 11 Feb 2013 09:24:01 +0100	[thread overview]
Message-ID: <20130211092401.086be57e@skate> (raw)
In-Reply-To: <201302100047.23872.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sun, 10 Feb 2013 00:47:23 +0100, Yann E. MORIN wrote:

> I would add arrows to the lines, to further ensure that what is
> dark-green and brown is input to buildroot, while what is gray
> is the output.

I would love to as well, but arrows are not immediately available in
Inkscape, you have to draw them manually. And since my designer skills
are very, very limited, I gave up on this.

> Besides, I've counted packages with:
>     $ grep -r -E -e '^[^[:space:]]+_VERSION[[:space:]]*:?='   \
>     | $(find package/ -type f -name '*.mk')                 \
>     | wc -l
>     944
> 
> So you can bump the number of packages to 900+. But beware: be
> consistent between the poster and the slides.

Indeed, thanks.

> >  * Give me suggestions on what to demonstrate. I will prepare a
> >    slideshow of 10-20 slides that continuously loops (it should
> 
> 20 slides is too much. The people attending wil not have time to wait
> to see the complete slideshow, so I'd stick with no more than 10
> slides with a very few points in each, switching after 7-10 seconds.

Ok. I will see how many topics I believe should be mentioned. But I
don't think we need to limit those too much: people don't necessarily
need to watch the entire slide set. As long as they get some of the
information, that's good enough.

> Points for those slides (out-of-order, obviously):

Thanks for those suggestions!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-02-11  8:24 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 [this message]
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=20130211092401.086be57e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.