From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Fix externals-deps and source-check when building out of tree
Date: Mon, 30 Aug 2010 16:20:02 +0200 [thread overview]
Message-ID: <877hj8xjvx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4C7BB4D7.4020909@carallon.com> (William Wagner's message of "Mon, 30 Aug 2010 14:40:39 +0100")
>>>>> "William" == William Wagner <will_wagner@carallon.com> writes:
Hi,
William> Ok, I'll take a look at your fix to see what I did wrong!
The problem is that if you always pass O=<dir>, then it will look in
output/.config instead of ./.config when the user isn't using O=<dir>
>> I see your patch is named 4/4, but I don't see any other patches from
>> you around that day - Was that just a mistake or did they get lost
>> somehow?
>>
William> Was putting together some other patches for new packages, thought I'd
William> send them after this release. Still not quite got the hang of git
William> send-email.
Ok.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-08-30 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 10:28 [Buildroot] [PATCH 4/4] Fix externals-deps and source-check when building out of tree Will Wagner
2010-08-29 21:28 ` Peter Korsgaard
2010-08-30 13:40 ` William Wagner
2010-08-30 14:20 ` 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=877hj8xjvx.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