From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2011-01-06
Date: Fri, 07 Jan 2011 15:44:04 -0700 [thread overview]
Message-ID: <4D279734.4@mentor.com> (raw)
In-Reply-To: <4D266CA1.4060306@mentor.com>
On 01/06/2011 06:30 PM, Tom Rini wrote:
> On 01/06/2011 04:22 PM, Cliff Brake wrote:
>> master has been merged to testing-next and is ready for clean builds.
>>
>> There are only 7 combinations listed as passing. If anyone has data
>> that is not entered, I'll check back tomorrow morning before I create
>> the tag.
>>
>> For more information on OpenEmbedded testing, see:
>>
>> http://www.openembedded.org/index.php/Testing
>>
>> We have lost some momentum with testing, so it would be nice to pick
>> up this effort again (speaking to myself first). I just ordered a 2TB
>> drive, so hopefully that will give me the capacity to do some more
>> builds.
>
> I see that the testing branch does contain the super long path fixes I
> pushed today so I expect to finally be able to push some real results
> (and failures!) over to the wiki this week. Build has started.
So, unfortunately the help2man fix I pushed today is also needed to get
a lot of things pushed towards building. I'm also working on building
(so I can test) moving the qemu boards over to xserver-xorg & co from
kdrive since we can get build failures if xserver-kdrive is the winner
(or provided anything at all? Not sure off the top of my head) for some
headers as other parts of X11R7.5 say "too old!" and bail.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-01-07 22:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 23:22 testing branch 2011-01-06 Cliff Brake
2011-01-07 1:30 ` Tom Rini
2011-01-07 8:00 ` Frans Meulenbroeks
2011-01-07 22:44 ` Tom Rini [this message]
2011-01-10 16:37 ` Tom Rini
2011-01-07 14:16 ` Cliff Brake
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=4D279734.4@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/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