From: Marcel Holtmann <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 176d01: build: Update library version
Date: Thu, 24 Aug 2023 07:10:01 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/8b2f00-176d01@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 176d0154b7f8ce16051762bf53cefa2935b08996
https://github.com/bluez/bluez/commit/176d0154b7f8ce16051762bf53cefa2935b08996
Author: Marcel Holtmann <marcel@holtmann.org>
Date: 2023-08-24 (Thu, 24 Aug 2023)
Changed paths:
M Makefile.am
Log Message:
-----------
build: Update library version
reply other threads:[~2023-08-24 14:10 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/8b2f00-176d01@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.