From: Andrew Shadura <andrew.shadura@collabora.co.uk>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/7] dbus: merge .bb and .inc
Date: Tue, 29 Sep 2015 16:52:17 +0200 [thread overview]
Message-ID: <560AA5A1.1090309@collabora.co.uk> (raw)
In-Reply-To: <1443538247.5162.43.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On 29/09/15 16:50, Richard Purdie wrote:
> On Tue, 2015-09-29 at 15:41 +0100, Burton, Ross wrote:
>> > On 29 September 2015 at 13:39, Andrew Shadura
>> > <andrew.shadura@collabora.co.uk> wrote:
>> >> There hasn't been anything on this for two weeks already, has
>> >> anyone
>> >> considered merging these patches?
>> >
>> > Sorry but they didn't quite make the M3 deadline (well, the patches
>> > did, but reviewing didn't as we were heads down trying to fix the
>> > build). If you can rebase and resend when master re-opens (when 2.0
>> > is released) that would be much appreciated.
> Just to add that what would help is a little bit more explanation about
> what happened in the patches. It looks like dbus-glib isn't needed for
> example but the commit message doesn't mention why?
Thanks. I will update the patches when I submit them next time.
--
Cheers,
Andrew
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-09-29 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1440666021-11411-1-git-send-email-andrew.shadura@collabora.co.uk>
2015-09-14 10:07 ` [PATCH v2 1/7] dbus: merge .bb and .inc Andrew Shadura
2015-09-14 10:07 ` [PATCH v2 2/7] dbus: update the recipes to 1.10.0 Andrew Shadura
2015-09-14 10:07 ` [PATCH v2 3/7] dbus: add apparmor support Andrew Shadura
2015-09-14 10:07 ` [PATCH v2 4/7] systemd: don't build against dbus unless required Andrew Shadura
2015-09-14 10:07 ` [PATCH v2 5/7] systemd: add gnuefi package configuration option, switched off by default Andrew Shadura
2015-09-14 10:07 ` [PATCH v2 6/7] dbus: add user sessions support Andrew Shadura
2015-09-14 10:07 ` [PATCH v2 7/7] dbus: build with systemd support Andrew Shadura
2015-09-29 12:39 ` [PATCH v2 1/7] dbus: merge .bb and .inc Andrew Shadura
2015-09-29 14:41 ` Burton, Ross
2015-09-29 14:48 ` Andrew Shadura
2015-09-29 14:54 ` Burton, Ross
2015-09-29 14:50 ` Richard Purdie
2015-09-29 14:52 ` Andrew Shadura [this message]
2015-09-14 10:41 ` [PATCH v3 1/2] dbus: add user sessions support Andrew Shadura
2015-09-14 10:41 ` [PATCH v3 2/2] dbus: build with systemd support Andrew Shadura
2015-09-15 11:36 ` [PATCH v3 1/2] dbus: add user sessions support Tanu Kaskinen
2015-09-15 11:48 ` Pau Espin Pedrol
2015-09-15 12:53 ` Andrew Shadura
2015-09-15 13:49 ` Tanu Kaskinen
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=560AA5A1.1090309@collabora.co.uk \
--to=andrew.shadura@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox