From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Handle gconf schema in gst-plugins-good
Date: Thu, 20 Oct 2011 11:40:36 -0700 [thread overview]
Message-ID: <cover.1319135920.git.josh@linux.intel.com> (raw)
Thanks to Koen's feedback this updated patch correctly ships the gconf schema with
the gconfelements package.
Cheers,
Joshua
The following changes since commit 99da9a4e65f9dffb04efc3ad60125194c476d6b3:
distro-tracking-fields: update fields for tzdata and gst-plugins-good (2011-10-20 13:07:16 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib josh/work
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/work
Joshua Lock (1):
gst-plugins-good: correctly handle gconf schema
.../gstreamer/gst-plugins-good_0.10.30.bb | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
--
1.7.6.4
next reply other threads:[~2011-10-20 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 18:40 Joshua Lock [this message]
2011-10-20 18:40 ` [PATCH 1/1] gst-plugins-good: correctly handle gconf schema Joshua Lock
2011-10-20 18:45 ` Martin Jansa
2011-10-20 18:49 ` Joshua Lock
2011-10-24 16:18 ` 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.1319135920.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox