From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [BlueZ v2 0/7] Port text docs to RST
Date: Tue, 20 Jan 2026 18:18:45 +0100 [thread overview]
Message-ID: <20260120172034.3463151-1-hadess@hadess.net> (raw)
So they can be integrated into our upcoming HTML docs. See:
https://hadess.github.io/bluez/
for a preview.
Changes since v1:
- Fix distcheck
Bastien Nocera (7):
doc: Port assigned-numbers.txt to RST
doc: Port thermometer-api.txt to RST
doc: Port security-bugs.txt to RST
doc: Port coding-style.txt to RST
doc: Port sap-api.txt to RST
doc: Port maintainer-guidelines.txt to RST
doc: Port health-api.txt to RST
Makefile.am | 30 +-
doc/assigned-numbers.rst | 29 ++
doc/assigned-numbers.txt | 26 --
doc/coding-style.rst | 349 ++++++++++++++++++
doc/coding-style.txt | 279 --------------
doc/health-api.txt | 152 --------
...idelines.txt => maintainer-guidelines.rst} | 61 +--
doc/org.bluez.HealthChannel.rst | 72 ++++
doc/org.bluez.HealthDevice.rst | 94 +++++
doc/org.bluez.HealthManager.rst | 68 ++++
doc/org.bluez.SimAccess.rst | 40 ++
doc/org.bluez.Thermometer.rst | 51 +++
doc/org.bluez.ThermometerManager.rst | 64 ++++
doc/org.bluez.ThermometerWatcher.rst | 79 ++++
doc/sap-api.txt | 20 -
doc/{security-bugs.txt => security-bugs.rst} | 1 +
doc/thermometer-api.txt | 134 -------
17 files changed, 908 insertions(+), 641 deletions(-)
create mode 100644 doc/assigned-numbers.rst
delete mode 100644 doc/assigned-numbers.txt
create mode 100644 doc/coding-style.rst
delete mode 100644 doc/coding-style.txt
delete mode 100644 doc/health-api.txt
rename doc/{maintainer-guidelines.txt => maintainer-guidelines.rst} (65%)
create mode 100644 doc/org.bluez.HealthChannel.rst
create mode 100644 doc/org.bluez.HealthDevice.rst
create mode 100644 doc/org.bluez.HealthManager.rst
create mode 100644 doc/org.bluez.SimAccess.rst
create mode 100644 doc/org.bluez.Thermometer.rst
create mode 100644 doc/org.bluez.ThermometerManager.rst
create mode 100644 doc/org.bluez.ThermometerWatcher.rst
delete mode 100644 doc/sap-api.txt
rename doc/{security-bugs.txt => security-bugs.rst} (99%)
delete mode 100644 doc/thermometer-api.txt
--
2.52.0
next reply other threads:[~2026-01-20 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 17:18 Bastien Nocera [this message]
2026-01-20 17:18 ` [BlueZ v2 1/7] doc: Port assigned-numbers.txt to RST Bastien Nocera
2026-01-20 18:34 ` Port text docs " bluez.test.bot
2026-01-20 17:18 ` [BlueZ v2 2/7] doc: Port thermometer-api.txt " Bastien Nocera
2026-01-20 17:18 ` [BlueZ v2 3/7] doc: Port security-bugs.txt " Bastien Nocera
2026-01-20 17:18 ` [BlueZ v2 4/7] doc: Port coding-style.txt " Bastien Nocera
2026-01-20 17:18 ` [BlueZ v2 5/7] doc: Port sap-api.txt " Bastien Nocera
2026-01-20 17:18 ` [BlueZ v2 6/7] doc: Port maintainer-guidelines.txt " Bastien Nocera
2026-01-20 17:18 ` [BlueZ v2 7/7] doc: Port health-api.txt " Bastien Nocera
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=20260120172034.3463151-1-hadess@hadess.net \
--to=hadess@hadess.net \
--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