From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing branch 2010-11-12
Date: Sun, 14 Nov 2010 11:38:02 -0700 [thread overview]
Message-ID: <4CE02C8A.2040002@mentor.com> (raw)
In-Reply-To: <AANLkTinuoktvgvT9V7OX1=FkMfeAgztmDaOCFMdH5x7d@mail.gmail.com>
On 11/14/2010 11:11 AM, Frans Meulenbroeks wrote:
> 2010/11/12 Cliff Brake<cliff.brake@gmail.com>:
>> testing-next is ready for clean builds. Not many builds succeeded
>> last week--I suspect people have been busy:
>
> Actually my builds also succeeded (apart from the neek one which seem
> to require some more love). The autobuilder did it's job quite nicely,
> but I was just not around to verify the results and update the page.
> The neek requires at least the os2 patch.
>
> Testing 2010-11-12 gives the same results. updated the testing page.
After my first week of doing some testing branch test builds I was
thinking, would some form of either automated result submitting or
form-based result submitting be a good idea? We could try and use a
google doc spreadsheet / form, for example. Thoughts?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-11-14 18:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 5:17 testing branch 2010-11-12 Cliff Brake
2010-11-14 18:11 ` Frans Meulenbroeks
2010-11-14 18:38 ` Tom Rini [this message]
2010-11-14 19:23 ` Yury Bushmelev
2010-11-14 20:32 ` Tom Rini
2010-11-15 15:46 ` Gary Thomas
2010-11-15 15:47 ` Cliff Brake
2010-11-15 18:07 ` Tom Rini
2010-11-15 20:22 ` Yuri Bushmelev
2010-11-18 22:13 ` Cliff Brake
2010-11-19 9:11 ` Petr Štetiar
2010-11-19 9:43 ` Frans Meulenbroeks
2010-11-19 10:16 ` Yury Bushmelev
2010-11-19 10:36 ` Petr Štetiar
2010-11-29 19:04 ` Cliff Brake
2011-01-04 10:36 ` Steffen Sledz
2011-01-07 14:17 ` 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=4CE02C8A.2040002@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