From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2010.02 on LinuxFr.org
Date: Mon, 8 Mar 2010 21:45:00 +0100 [thread overview]
Message-ID: <20100308214500.34290fb1@surf> (raw)
Hello,
I have submitted a news heading about Buildroot 2010.02 on LinuxFr.org,
the most important french news website of the open-source / free
software community. The news has been published at:
http://linuxfr.org/2010/03/08/26560.html
In the news, I sum up what Buildroot is for, what the history of the
project is, what changes have been made in 2010.02, and some of the
changes we intend to do in 2010.05.
I also mention that the french Linux Magazine will publish on March,
12th a new issue, with two articles about Buildroot. I have no idea
what their contents will be, nor who has written them. I'll report
about them as soon as the magazine will be available.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
reply other threads:[~2010-03-08 20:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100308214500.34290fb1@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