Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: QEMU recipe cleanup
Date: Wed, 22 Feb 2012 23:15:27 +0000	[thread overview]
Message-ID: <1329952527.32110.43.camel@ted> (raw)
In-Reply-To: <2449634.H5BiXpsY7e@helios>

On Wed, 2012-02-22 at 15:21 +0000, Paul Eggleton wrote:
> Hi all,
> 
> I was looking into Yocto bug #2020 today and I noticed we have some "old" QEMU 
> recipes kicking around. 0.15.1 is the latest version which AFAIK I've been 
> using since it was merged mid-October last year, and it seems to be working 
> fine. We also have 0.14.0 and a _git recipe which claims (via manually set PV) 
> to be 0.14.0 as well.
> 
> Do we need to keep all of these?

I'd axe the 0.14 version if nobody shouts. I think it was kept as 0.15
changed a lot of things and we had some issues. I think they're all
resolved now though.

Cheers,

Richard




      reply	other threads:[~2012-02-22 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 15:21 QEMU recipe cleanup Paul Eggleton
2012-02-22 23:15 ` Richard Purdie [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=1329952527.32110.43.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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