From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1]l3afpad: Use distro_features_check for gtk+3
Date: Wed, 29 Jun 2016 11:28:58 +0800 [thread overview]
Message-ID: <5773407A.4080607@windriver.com> (raw)
In-Reply-To: <cover.1467170719.git.hongxu.jia@windriver.com>
This fix is duplicated with Joe Slater's "l3afpad: add check for
GTK3DISTROFEATURES"
Please drop this one.
//Hongxu
On 2016年06月29日 11:26, Hongxu Jia wrote:
> The following changes since commit 13eb4a832b533f84001fca8be960ad1e58fc823f:
>
> gst-player: upgrade to latest HEAD (2016-06-27 14:08:43 +0100)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib hongxu/fix-l3afpad
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=hongxu/fix-l3afpad
>
> Hongxu Jia (1):
> l3afpad: Use distro_features_check for gtk+3
>
> meta/recipes-sato/l3afpad/l3afpad_git.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
prev parent reply other threads:[~2016-06-29 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 3:26 [PATCH 0/1]l3afpad: Use distro_features_check for gtk+3 Hongxu Jia
2016-06-29 3:26 ` [PATCH 1/1] l3afpad: " Hongxu Jia
2016-06-29 3:28 ` Hongxu Jia [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=5773407A.4080607@windriver.com \
--to=hongxu.jia@windriver.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