From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing 2010-12-10 (wiki, results, bluez-libs)
Date: Wed, 15 Dec 2010 07:43:01 -0700 [thread overview]
Message-ID: <4D08D3F5.1060608@mentor.com> (raw)
In-Reply-To: <AANLkTimTaZyPywc_B8g4k4QO+gTJq67K=OgcoSe6BpJh@mail.gmail.com>
On 12/15/2010 12:51 AM, Frans Meulenbroeks wrote:
> Dear all,
>
> I just wanted to update the testing table with my entries and I
> noticed two (possibly related) things.
> - no other entries for 2010-12-10 are there yet (and it is already wednesday)
I haven't updated the stuff we're building since just about everything
failed due to the gcc issue Khem fixed in
2c8570552549da2e11428d08b2bc08849cac39b1. This is why I sometimes
wonder if it would be desirable to cherry-pick a few things in to the
testing-next branch.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-12-15 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 7:51 testing 2010-12-10 (wiki, results, bluez-libs) Frans Meulenbroeks
2010-12-15 14:43 ` Tom Rini [this message]
2010-12-15 15:33 ` Frans Meulenbroeks
2010-12-15 17:23 ` Tom Rini
2010-12-15 18:41 ` Frans Meulenbroeks
2010-12-16 13:33 ` Cliff Brake
2010-12-16 15:55 ` Khem Raj
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=4D08D3F5.1060608@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.