From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] make menuconfig in a buildroot env.
Date: Wed, 7 Mar 2007 15:44:52 +0100 [thread overview]
Message-ID: <20070307144452.GC16872@aon.at> (raw)
In-Reply-To: <20070223103342.GD30949@zelow.no>
On Fri, Feb 23, 2007 at 11:33:42AM +0100, Thomas Lundquist wrote:
>On Fri, Feb 23, 2007 at 10:14:33AM +0100, Thomas Lundquist wrote:
>
>And I wonder why I didn't think about it but this patch copies the
>missing .h file into the target dir.
Applied, thanks.
prev parent reply other threads:[~2007-03-07 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 19:50 [Buildroot] make menuconfig in a buildroot env Thomas Lundquist
2007-02-23 6:56 ` Thomas Lundquist
2007-02-23 8:19 ` Philippe Ney
2007-02-23 9:14 ` Thomas Lundquist
2007-02-23 10:33 ` Thomas Lundquist
2007-03-07 14:44 ` Bernhard Fischer [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=20070307144452.GC16872@aon.at \
--to=rep.dot.nop@gmail.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