From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot article in Mind newsletter
Date: Fri, 28 Aug 2015 21:59:07 +0200 [thread overview]
Message-ID: <871tenw5f8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <55DF2D35.2050302@mind.be> (Arnout Vandecappelle's message of "Thu, 27 Aug 2015 17:31:01 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
> Hi all,
> I wrote a short article for my company's newsletter (which we try to fill with
> interesting stuff rather than commercial blabla) about recent (= last 5 years)
> developments in Buildroot. If anyone is interested, you can read it on our
> website [1]. It's CC-BY-SA licensed so you can reuse the text. You can download
> the source here[2].
> Note: the newsletter will only be sent out tomorrow, so if you think I'm
> writing something that's incorrect or not very good and it should be changed,
> there's still a bit of time...
Sorry, I'm running a bit late, but that's a very nice article, great!
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2015-08-28 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 15:31 [Buildroot] Buildroot article in Mind newsletter Arnout Vandecappelle
2015-08-27 17:52 ` Thomas De Schampheleire
2015-08-27 18:02 ` Thomas Petazzoni
2015-08-28 19:59 ` Peter Korsgaard [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=871tenw5f8.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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