From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] Fix and update clutter-1.6
Date: Tue, 19 Apr 2011 15:49:40 -0700 [thread overview]
Message-ID: <cover.1303253280.git.josh@linux.intel.com> (raw)
From: Joshua Lock <josh@linux.intel.com>
Same as the v1 patch set only with an extra patch to update to the latest
release in the Clutter 1.6 stable series.
With a recent patchset I changed clutter to depend on a json-glib recipe then
promptly didn't include that recipe in the patch series - apologies.
Further I've removed a patch from the 1.6 recipe which is no longer required.
Finally, Clutter 1.6.14 - hurrah!
Pull URL: git://git.openembedded.org/openembedded-core-contrib
Branch: josh/clutter
Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/clutter
Thanks,
Joshua Lock <josh@linux.intel.com>
---
Joshua Lock (3):
json-glib: new recipe required by clutter
clutter-1.6: drop no longer required patch
clutter-1.6: update to 1.6.14
meta/recipes-gnome/json-glib/json-glib_0.12.2.bb | 20 ++++++++++++++++++++
...{clutter-1.6_1.6.8.bb => clutter-1.6_1.6.14.bb} | 9 ++++-----
2 files changed, 24 insertions(+), 5 deletions(-)
create mode 100644 meta/recipes-gnome/json-glib/json-glib_0.12.2.bb
rename meta/recipes-graphics/clutter/{clutter-1.6_1.6.8.bb => clutter-1.6_1.6.14.bb} (66%)
--
1.7.4.4
next reply other threads:[~2011-04-19 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 22:49 Joshua Lock [this message]
2011-04-19 22:49 ` [PATCH v2 1/3] json-glib: new recipe required by clutter Joshua Lock
2011-04-19 22:49 ` [PATCH v2 3/3] clutter-1.6: update to 1.6.14 Joshua Lock
2011-04-19 22:49 ` [PATCH v2 2/3] clutter-1.6: drop no longer required patch Joshua Lock
2011-04-19 23:10 ` [PATCH v2 0/3] Fix and update clutter-1.6 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=cover.1303253280.git.josh@linux.intel.com \
--to=josh@linux.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.