All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Release-2011.03 status
Date: Mon, 28 Feb 2011 11:48:18 -0700	[thread overview]
Message-ID: <4D6BEDF2.20006@mentor.com> (raw)
In-Reply-To: <20110228170111.GB4192@excalibur.local>

On 02/28/2011 10:01 AM, Stefan Schmidt wrote:
> Hello.
>
> On Mon, 2011-02-28 at 08:31, Tom Rini wrote:
>>
>> So, my current plan of attack is to do what I've said before and
>> merge the libvpx work-around, tag, revert the libvpx work-around
>> (per Khem's request).  And I plan to do this tomorrow unless people
>> shout about wanting to fix something they know is broken and need a
>> little more time.
>
> For llvm and thus openjdk-6 we need the patch merged I posted today. I'm not
> completely sure that it is the best solutions thats why I posted it instead of
> just commit it.

Hmm, can you show the failure log?  Thanks!

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2011-02-28 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 15:31 Release-2011.03 status Tom Rini
2011-02-28 17:01 ` Stefan Schmidt
2011-02-28 18:48   ` Tom Rini [this message]
2011-03-01 18:16     ` Stefan Schmidt

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=4D6BEDF2.20006@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.