From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 798da8: doc: Add commit message guidelines for AI coding a...
Date: Thu, 01 Oct 2026 13:33:52 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/549f3d-ae69dc@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 798da8d7ace22ff23c0644d4fd92c67997638280
https://github.com/bluez/bluez/commit/798da8d7ace22ff23c0644d4fd92c67997638280
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M doc/coding-assistants.rst
Log Message:
-----------
doc: Add commit message guidelines for AI coding assistants
Require commit messages to record only the changes and their rationale,
to follow Rule 2 of the maintainer guidelines, and to have their factual
claims checked against the diff.
Inspired by WirePlumber's AGENTS.md:
https://gitlab.freedesktop.org/pipewire/wireplumber/-/blob/master/AGENTS.md
Assisted-by: OpenCode:claude-opus-5.5
Commit: 17ea5080c481c2acfb6c532f602bf2028deba918
https://github.com/bluez/bluez/commit/17ea5080c481c2acfb6c532f602bf2028deba918
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M doc/coding-assistants.rst
Log Message:
-----------
doc: Add bug fixing procedure for AI coding assistants
Require AI assistants fixing bugs to verify them with a reproducer, test
the fix, state what could not be verified and leave any submission to
the human, with vulnerabilities following SECURITY.md.
Adapted from the Linux kernel's
Documentation/process/coding-assistants.rst.
Assisted-by: OpenCode:claude-opus-5.5
Commit: 2f1ae1462507a1e1a9eb33bfc88d3b8741b50e80
https://github.com/bluez/bluez/commit/2f1ae1462507a1e1a9eb33bfc88d3b8741b50e80
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
A AGENTS.md
Log Message:
-----------
Add AGENTS.md symlink to doc/coding-assistants.rst
Let AI coding assistants that look for AGENTS.md load the guidelines
automatically.
Assisted-by: OpenCode:claude-opus-5.5
Commit: bb98c3e02282c0383aa75651d754afd50fc385d2
https://github.com/bluez/bluez/commit/bb98c3e02282c0383aa75651d754afd50fc385d2
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M doc/mgmt-protocol.rst
M lib/bluetooth/mgmt.h
Log Message:
-----------
mgmt: Add Security Level Changed event
This provides a TLV list of values related to the security level of
the connection to a remote device.
Currently Security Level and Encryption type are implemented.
Commit: 74334ac97049c8d878de9b76e6f89f0393a2c202
https://github.com/bluez/bluez/commit/74334ac97049c8d878de9b76e6f89f0393a2c202
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M tools/mgmt-tester.c
Log Message:
-----------
mgmt-tester: Add Security Level Changed event tests
Test that MGMT_EV_SECURITY_LEVEL_CHANGED is correctly received during
BREDR and LE secured connection.
Assisted-by: GPT:GPT-5.3-Codex
Commit: 1391af1995a9b07a344e872d019447e315ef0486
https://github.com/bluez/bluez/commit/1391af1995a9b07a344e872d019447e315ef0486
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M monitor/packet.c
Log Message:
-----------
monitor: Add support for Mgmt Security Level changed event
@ MGMT Event: Security Level Changed (0x0034) plen 16
BR/EDR Address: 00:AA:01:01:00:00 (Intel Corporation)
Security Level: No security (0x00000000)
Encryption Type: No encryption (0x00000000)
Commit: 09e58eb8da1b4d65857db900b8914173ecdd5644
https://github.com/bluez/bluez/commit/09e58eb8da1b4d65857db900b8914173ecdd5644
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M src/adapter.c
M src/device.c
M src/device.h
Log Message:
-----------
device: Add SecurityLevel properties to org.bluez.Device1
This uses the new MGMT_EV_SECURITY_LEVEL_CHANGED event.
It will be used by btpclient to reduce test time.
Commit: d3f2b6f3e142427f21eede2e7379f28e22b106c6
https://github.com/bluez/bluez/commit/d3f2b6f3e142427f21eede2e7379f28e22b106c6
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M doc/org.bluez.Device.rst
Log Message:
-----------
org.bluez.Device: Add Security Level related properties
This adds the SecurityLevel and EncryptionType properties which can be
used by clients to get the security level and encryption type in use
for a connection.
Commit: ae69dcddd5495c7c72b7935e12e17cf6d6b28461
https://github.com/bluez/bluez/commit/ae69dcddd5495c7c72b7935e12e17cf6d6b28461
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2026-10-01 (Thu, 01 Oct 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Display SecurityLevel in device info
Compare: https://github.com/bluez/bluez/compare/549f3d50686b...ae69dcddd549
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-10-01 20:33 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/master/549f3d-ae69dc@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