From: patchwork-bot+bluetooth@kernel.org
To: Gioele Barabucci <gioele@svario.it>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v4 0/2] configure.ac: Install D-Bus policy in /usr/share, not /etc
Date: Wed, 09 Aug 2023 18:20:21 +0000 [thread overview]
Message-ID: <169160522100.14644.4519904446970876636.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230809065143.2002324-1-gioele@svario.it>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 9 Aug 2023 08:51:41 +0200 you wrote:
> [Sending again, this time with the right commit titles. Sorry for the noise.]
>
> This patch changes configure.am to install the bluez D-Bus policy in
> `/usr/share/dbus-1/system.d` instead of `/etc/dbus-1/system.d`.
>
> From https://bugs.debian.org/1006631:
>
> [...]
Here is the summary with links:
- [BlueZ,v4,1/2] configure.ac: Bump minimum D-Bus version to 1.10
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8b6432a8728f
- [BlueZ,v4,2/2] configure.ac: Install D-Bus policy in /usr/share, not /etc
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fc6f5856d177
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-09 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 6:51 [PATCH BlueZ v4 0/2] configure.ac: Install D-Bus policy in /usr/share, not /etc Gioele Barabucci
2023-08-09 6:51 ` [PATCH BlueZ v4 1/2] configure.ac: Bump minimum D-Bus version to 1.10 Gioele Barabucci
2023-08-09 8:25 ` configure.ac: Install D-Bus policy in /usr/share, not /etc bluez.test.bot
2023-08-09 6:51 ` [PATCH BlueZ v4 2/2] " Gioele Barabucci
2023-08-09 18:20 ` patchwork-bot+bluetooth [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=169160522100.14644.4519904446970876636.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=gioele@svario.it \
--cc=linux-bluetooth@vger.kernel.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