From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH v2] dbus 1.4.1: create UUIDDIR in postinst
Date: Fri, 27 May 2011 16:35:07 +0100 [thread overview]
Message-ID: <1306510507.27470.274.camel@rex> (raw)
In-Reply-To: <1306507308-8674-1-git-send-email-koen@dominion.thruhere.net>
On Fri, 2011-05-27 at 16:41 +0200, Koen Kooi wrote:
> This fixes dbus usage in non-sysV init systems. Volatiles aren't needed in systemd land, since /run is tmpfs and the dbus units take care of all this.
>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>
> Changes since v1:
>
> * addressed pbs concerns about the || true and chgrp dots
> * check for volatiles before trying to run the script
>
> meta/recipes-core/dbus/dbus.inc | 12 +++++++++---
> meta/recipes-core/dbus/dbus_1.4.1.bb | 2 +-
> 2 files changed, 10 insertions(+), 4 deletions(-)
Applied to master, thanks.
Richard
prev parent reply other threads:[~2011-05-27 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 14:41 [PATCH v2] dbus 1.4.1: create UUIDDIR in postinst Koen Kooi
2011-05-27 15:35 ` Richard Purdie [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=1306510507.27470.274.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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