From: Zhong Hongbo <hongbo.zhong@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] bluez4: Fix no moudle named gi.repository and GObject for simpel-agent
Date: Thu, 14 Nov 2013 11:30:29 +0800 [thread overview]
Message-ID: <528443D5.8020105@windriver.com> (raw)
In-Reply-To: <CAJTo0LZZhEF5S9anD54RrrVyGe07KkdNhTh1gz=giRJk_n7k7A@mail.gmail.com>
On 11/13/2013 08:30 PM, Burton, Ross wrote:
> On 13 November 2013 10:08, Zhong Hongbo <hongbo.zhong@windriver.com> wrote:
>> +++ b/meta/recipes-connectivity/bluez/bluez4-4.101/fix-no-module-name-GObject-for-simple-agent.patch
>> @@ -0,0 +1,25 @@
>> +Fix No module name gi.repository and GObject for simple-agent
>> +
>> +Signed-off-by: Zhong Hongbo <hongbo.zhong@windriver.com>
> Patch needs an Upstream-Status ("Inappropriate [revert]" would be
> suitable), and please rename the patch/comment to something more
> accurate along the lines of "use legacy pygobject instead of
> gobject-introspection".
Sorry, This is my first RR. I will do it in the next RR.
Thanks,
Hongbo
>
> Ross
>
>
next prev parent reply other threads:[~2013-11-14 3:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 10:08 [PATCH 0/2] bluez4: Install and fix simpe-agent Zhong Hongbo
2013-11-13 10:08 ` [PATCH 1/2] bluez4: Install simple-agent utility for pairing bluetooth devices Zhong Hongbo
2013-11-13 11:38 ` Phil Blundell
2013-11-13 12:34 ` Burton, Ross
2013-11-13 13:24 ` Philip Balister
2013-11-13 14:50 ` Burton, Ross
2013-11-14 3:29 ` Zhong Hongbo
2013-11-13 10:08 ` [PATCH 2/2] bluez4: Fix no moudle named gi.repository and GObject for simpel-agent Zhong Hongbo
2013-11-13 12:30 ` Burton, Ross
2013-11-14 3:30 ` Zhong Hongbo [this message]
2013-11-14 10:47 ` Zhong Hongbo
2013-11-14 10:53 ` Burton, Ross
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=528443D5.8020105@windriver.com \
--to=hongbo.zhong@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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.