From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Upgrade waffle and fix recipe issues
Date: Wed, 27 May 2015 11:16:36 +0300 [thread overview]
Message-ID: <cover.1432713868.git.jussi.kukkonen@intel.com> (raw)
I've tried to fix the package configuration already in the recipe to
do what I think it was trying to do. If there is nowadays a smarter
way to set config based on the capabilities of the GL stack, do let me
know.
The following changes since commit a05663bfa10352fd5af6ca9a9d7b323c1c099f35:
distro/upstream_tracking: remove stale update reasons (2015-05-26 22:43:46 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jku/waffle
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/waffle
Jussi Kukkonen (1):
waffle: Upgrade 1.3.0 -> 1.5.1
.../waffle/{waffle_1.3.0.bb => waffle_1.5.1.bb} | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
rename meta/recipes-graphics/waffle/{waffle_1.3.0.bb => waffle_1.5.1.bb} (51%)
--
2.1.4
next reply other threads:[~2015-05-27 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 8:16 Jussi Kukkonen [this message]
2015-05-27 8:16 ` [PATCH 1/1] waffle: Upgrade 1.3.0 -> 1.5.1 Jussi Kukkonen
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=cover.1432713868.git.jussi.kukkonen@intel.com \
--to=jussi.kukkonen@intel.com \
--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 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.