From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Merge request
Date: Thu, 27 May 2010 14:31:01 +0200 [thread overview]
Message-ID: <87bpc1v856.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100523105523.225c205b@surf> (Thomas Petazzoni's message of "Sun, 23 May 2010 10:55:23 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> On Sat, 22 May 2010 22:21:13 +0200
Thomas> Peter Korsgaard <jacmet@uclibc.org> wrote:
>> I'm not completely happy about adding that one this late in the
>> release cycle, but I've committed the other 3 - Thanks!
Thomas> Why ? This patch isn't modifying any existing code, it just adds new
Thomas> code. If this code is broken, well, then BeagleBoard support will not
Thomas> work, but otherwise it wouldn't be supported.
True, but I would like to sort out all the BR2_BOARD_NAME mess before
adding more, and I don't like the xload package using a "random" git
tree.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-05-27 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 8:29 [Buildroot] Merge request Thomas Petazzoni
2010-05-22 20:21 ` Peter Korsgaard
2010-05-23 8:55 ` Thomas Petazzoni
2010-05-27 12:31 ` 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=87bpc1v856.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