From: fdanis-oss <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 690ecc: mesh: Provide GNU basename compatible implementation
Date: Tue, 10 Sep 2024 12:32:34 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/54866c-615fc3@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 690eccbe8562cc33f33503af67beb313ca737817
https://github.com/bluez/bluez/commit/690eccbe8562cc33f33503af67beb313ca737817
Author: Khem Raj <raj.khem@gmail.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M configure.ac
M mesh/mesh-config-json.c
A mesh/missing.h
M mesh/rpl.c
M tools/hex2hcd.c
A tools/missing.h
Log Message:
-----------
mesh: Provide GNU basename compatible implementation
Call to basename() relies on a GNU extension
to take a const char * vs a char *. Let's define
a trivial helper function to ensure compatibility
with musl.
Fixes: https://github.com/bluez/bluez/issues/843
Commit: 615fc3592a57e32b42691a16b5d5cc88e378cbc1
https://github.com/bluez/bluez/commit/615fc3592a57e32b42691a16b5d5cc88e378cbc1
Author: Frédéric Danis <frederic.danis@collabora.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M gobex/gobex-header.c
Log Message:
-----------
gobex: Replace g_convert by utf16_to_utf8
The glibc's iconv implementation is based around plug in modules
for specific translations which may not been built on the platform
and prevent to use g_convert().
This commit replaces it by a function similar to the existing
utf8_to_utf16() function.
Compare: https://github.com/bluez/bluez/compare/54866cee3fad...615fc3592a57
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2024-09-10 19:32 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/54866c-615fc3@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.