From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 102f4b: The GATT.Client option is in the wrong section.
Date: Fri, 07 Nov 2025 05:03:47 -0800 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1020865/000000-102f4b@github.com> (raw)
Branch: refs/heads/1020865
Home: https://github.com/bluez/bluez
Commit: 102f4bc5e3da84972ee92e10b85e47c49e0ca539
https://github.com/bluez/bluez/commit/102f4bc5e3da84972ee92e10b85e47c49e0ca539
Author: Pavel Bozhko <pvbozhko@salutedevices.com>
Date: 2025-11-07 (Fri, 07 Nov 2025)
Changed paths:
M src/main.conf
Log Message:
-----------
The GATT.Client option is in the wrong section.
GATT.Client is currently in the CSIS section, but should
be in the GATT section. The bug is that
setting the Client option to false has no effect.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-11-07 13:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1020865/000000-102f4b@github.com \
--to=noreply@github.com \
--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;
as well as URLs for NNTP newsgroup(s).