From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Patrick Ohly" <patrick.ohly@intel.com>,
"Aníbal Limón" <anibal.limon@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] qemu: Upgrade to 2.7.1
Date: Mon, 23 Jan 2017 16:01:36 +0200 [thread overview]
Message-ID: <8c0f5529-3dbb-1049-dc59-0cb368e04359@linux.intel.com> (raw)
In-Reply-To: <1484941467.20333.3.camel@intel.com>
On 01/20/2017 09:44 PM, Patrick Ohly wrote:
> In contrast to Alexander, I would also keep
> http://wiki.qemu-project.org/download/${BP}.tar.bz2 in qemu_2.7.1.bb
> with SRC_URI =+ because then there can be a qemu_git.bb with a different
> URL than the one above.
I would discourage creation of such separate _git recipes, unless there
is a clear benefit to the whole of oe-core. They are almost always
untested and neglected, and eventually removed because they're outdated
and broken and no one cares.
Alex
next prev parent reply other threads:[~2017-01-23 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 18:12 [PATCHv2] qemu: Upgrade to 2.7.1 Aníbal Limón
2017-01-20 19:44 ` Patrick Ohly
2017-01-23 14:01 ` Alexander Kanavin [this message]
2017-01-23 14:29 ` Patrick Ohly
2017-01-23 14:32 ` Richard Purdie
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=8c0f5529-3dbb-1049-dc59-0cb368e04359@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=anibal.limon@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
/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.