From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] bbfeef: shell: Clarify "mode" variable
Date: Thu, 01 May 2025 09:17:48 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/f8d0dc-bbfeef@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: bbfeef3a04b0ad4de5802790b6bcb2e4d9fb9e5e
https://github.com/bluez/bluez/commit/bbfeef3a04b0ad4de5802790b6bcb2e4d9fb9e5e
Author: Bastien Nocera <hadess@hadess.net>
Date: 2025-05-01 (Thu, 01 May 2025)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shell: Clarify "mode" variable
It's unclear what that variable did, and which value corresponded to
which state, so replace it with a typed enum so that conditionals are
more easily parsed.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-05-01 16:17 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/f8d0dc-bbfeef@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.