From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ell 0.38 bluez 5.56
Date: Wed, 07 Apr 2021 16:15:08 +0200 [thread overview]
Message-ID: <20210407141508.uA7_X8JKF8Zm98U7JyG5dihZ1JB2NLWN_wOAsJxQHSo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28488@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/28488#issuecomment-814950478
Comment:
* 5.58 requires ell 0.39
* using `-n` flag in the service means that bluetoothd logs to stdout, could you add logging to the service? What's the policy about logging in services in Void? When should they be included in the package?
* could you add --enable-experimental flag to bluez as a build option? (disabled by default) This option should enable monitoring battery level with a dbus interface.
next prev parent reply other threads:[~2021-04-07 14:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 18:24 [PR PATCH] ell: update to 0.37 ericonr
2021-02-04 18:29 ` [PR PATCH] [Updated] " ericonr
2021-02-04 18:49 ` [NOMERGE] nell: " ericonr
2021-02-04 18:58 ` ericonr
2021-02-05 2:00 ` [NOMERGE] ell: " sgn
2021-02-05 2:06 ` ericonr
2021-02-05 2:06 ` ericonr
2021-02-05 2:06 ` ericonr
2021-02-05 2:07 ` ericonr
2021-02-05 2:07 ` ericonr
2021-02-05 2:11 ` sgn
2021-02-05 2:13 ` sgn
2021-02-26 20:23 ` [PR PATCH] [Updated] " ericonr
2021-02-27 0:15 ` iwd 1.12 ell 0.38 bluez 5.56 sgn
2021-03-01 15:07 ` sgn
2021-03-01 15:09 ` sgn
2021-03-01 18:25 ` ericonr
2021-03-11 20:48 ` [PR PATCH] [Updated] " ericonr
2021-03-11 20:49 ` ericonr
2021-04-07 14:00 ` paper42
2021-04-07 14:15 ` paper42 [this message]
2021-04-07 15:46 ` [PR PATCH] [Updated] " ericonr
2021-04-07 15:47 ` ericonr
2021-04-07 15:47 ` [PR PATCH] [Updated] " ericonr
2021-04-07 17:48 ` paper42
2021-04-10 11:01 ` paper42
2021-04-11 4:13 ` [PR PATCH] [Closed]: " ericonr
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=20210407141508.uA7_X8JKF8Zm98U7JyG5dihZ1JB2NLWN_wOAsJxQHSo@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).