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>
Subject: Re: [PATCH] bluez5: allow D-Bus to spawn obexd in systems without systemd
Date: Fri, 18 Mar 2016 16:33:22 +0100	[thread overview]
Message-ID: <56EC1FC2.1020502@digi.com> (raw)
In-Reply-To: <56E06C6D.5020008@digi.com>

On 09/03/16 19:33, Javier Viguera wrote:
> On 24/02/16 19:12, Javier Viguera wrote:
>> This includes a proper D-Bus service file for obexd in systems that do
>> not support systemd.
>>
>> Signed-off-by: Javier Viguera
>> <javier.viguera-i7dp0qKlBMg-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org>
>
> Ping.
>

I know people is probably busy enough trying to stabilize the upcoming 
2.1 release, but could this be considered for master?


Thanks,

Javier Viguera


  reply	other threads:[~2016-03-18 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 18:12 [PATCH] bluez5: allow D-Bus to spawn obexd in systems without systemd Javier Viguera
2016-03-09 18:33 ` Javier Viguera
2016-03-18 15:33   ` Javier Viguera [this message]
2016-03-18 18:48     ` Otavio Salvador
2016-03-18 20:04       ` 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=56EC1FC2.1020502@digi.com \
    --to=javier.viguera@digi.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