From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Developer Day, 29th October 2010
Date: Thu, 25 Nov 2010 20:55:54 +0100 [thread overview]
Message-ID: <20101125205554.42aacf9e@surf> (raw)
In-Reply-To: <20101125172129.GA20008@merkur.ravnborg.org>
On Thu, 25 Nov 2010 18:21:29 +0100
Sam Ravnborg <sam@ravnborg.org> wrote:
> Thought this was a nice write-up so I forwarded it to lwn.net.
> It is in their "Development" page for this weeks edition.
> Requires subscription to see it until next Thursday.
Thanks for doing this!
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:[~2010-11-25 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 21:14 [Buildroot] Report from the Buildroot Developer Day, 29th October 2010 Thomas Petazzoni
2010-11-23 22:02 ` Yann E. MORIN
2010-11-24 13:43 ` Peter Korsgaard
2010-11-25 17:21 ` Sam Ravnborg
2010-11-25 19:55 ` Thomas Petazzoni [this message]
2010-11-26 9:23 ` Peter Korsgaard
2010-11-26 12:16 ` Thomas De Schampheleire
2010-11-26 13:45 ` Thomas Petazzoni
2010-11-26 23:23 ` Yann E. MORIN
2010-11-27 17:13 ` 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=20101125205554.42aacf9e@surf \
--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