Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Javier Viguera <javier.viguera@digi.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	<joshua.g.lock@linux.intel.com>
Subject: Re: [jethro][PATCH] bluez5: allow D-Bus to spawn obexd in systems without systemd
Date: Mon, 21 Mar 2016 12:36:12 +0100	[thread overview]
Message-ID: <56EFDCAC.6080806@digi.com> (raw)
In-Reply-To: <1457004633.3025.13.camel@linux.intel.com>

Hi Joshua

On 03/03/16 12:30, Joshua G Lock wrote:
>
> Ah, I hadn't seen that patch as I was only looking at patches tagged
> jethro. We can consider this change for jethro once it lands in master.
>

This has been finally merged into master.

Would you now consider cherry-picking it into *jethro* ?

Thanks,

Javier Viguera


  reply	other threads:[~2016-03-21 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 18:14 [jethro][PATCH] bluez5: allow D-Bus to spawn obexd in systems without systemd Javier Viguera
2016-03-03 11:07 ` Joshua G Lock
2016-03-03 11:22   ` Viguera, Javier
2016-03-03 11:30     ` Joshua G Lock
2016-03-21 11:36       ` Javier Viguera [this message]
2016-03-22 10:37         ` Joshua G Lock

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=56EFDCAC.6080806@digi.com \
    --to=javier.viguera@digi.com \
    --cc=joshua.g.lock@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