Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot on LWN
Date: Fri, 30 Apr 2010 16:17:58 +0200	[thread overview]
Message-ID: <87pr1h6n3d.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <m2i2facd6dc1004290840k7197fe97o28cd32dc2b3260fd@mail.gmail.com> (Tom Parkin's message of "Thu, 29 Apr 2010 16:40:10 +0100")

>>>>> "Tom" == Tom Parkin <tom.parkin@gmail.com> writes:

Hi,

 Tom> Whilst we're on the subject, I just wanted to say thanks again to
 Tom> the folks who chimed in on my earlier thread about Buildroot's use
 Tom> in embedded projects.  Although I wasn't able to use all the
 Tom> examples, I think it really helps to be able to point to some
 Tom> real-life usage examples to help ground the discussion in
 Tom> something concrete.

You're welcome - Thanks for writing the article.


-- 
Bye, Peter Korsgaard

      reply	other threads:[~2010-04-30 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 12:22 [Buildroot] Buildroot on LWN Thomas Petazzoni
2010-04-29 15:40 ` Tom Parkin
2010-04-30 14:17   ` 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=87pr1h6n3d.fsf@macbook.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