From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [2010.02] Package infrastructure ready
Date: Thu, 10 Dec 2009 19:51:13 +0100 [thread overview]
Message-ID: <20091210195113.522e1c3e@surf> (raw)
In-Reply-To: <878wdepiz1.fsf@macbook.be.48ers.dk>
Le Mon, 07 Dec 2009 22:33:38 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> Sorry, my kids have been ill and I didn't got to read through your
> series yet - Give me a day or two and I will.
No problem.
The most important thing I need is an answer to the few questions I've
asked in the initial e-mail of this thread (technical details on the
implementation).
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-12-10 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 23:36 [Buildroot] [2010.02] Package infrastructure ready Thomas Petazzoni
2009-12-07 21:18 ` Thomas Petazzoni
2009-12-07 21:33 ` Peter Korsgaard
2009-12-10 18:51 ` Thomas Petazzoni [this message]
2009-12-08 10:22 ` Will Newton
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=20091210195113.522e1c3e@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