From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot talk at ELCE
Date: Fri, 25 Oct 2013 09:14:57 +0200 [thread overview]
Message-ID: <87ob6d7rf2.fsf@dell.be.48ers.dk> (raw)
FYI,
As you might be aware, I'm doing a talk titled 'Buildroot: What is new'
this afternoon at the Embedded Linux Conference Europe. See the link
below for the slides:
http://peter.korsgaard.com/buildroot-whats-new-elce2013.pdf
I'm trying to make it clear that Buildroot is very much alive, with lots
of activity.
Most items in the slides have already been discussed, but I would very
much appreciate if you could take a quick look and let me know if I
missed something important or said anything stupid.
Thanks!
--
Bye, Peter Korsgaard
next reply other threads:[~2013-10-25 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 7:14 Peter Korsgaard [this message]
2013-10-25 7:29 ` [Buildroot] Buildroot talk at ELCE Baruch Siach
2013-10-25 7:41 ` Peter Korsgaard
2013-10-25 7:42 ` Thomas De Schampheleire
2013-10-25 7:47 ` Peter Korsgaard
2013-10-25 7:53 ` Arnout Vandecappelle
2013-10-25 7:57 ` Peter Korsgaard
2013-10-25 8:00 ` Arnout Vandecappelle
2013-10-25 8:02 ` Thomas De Schampheleire
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=87ob6d7rf2.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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