From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ v3 0/9] Port text docs to RST and move man pages
Date: Thu, 22 Jan 2026 16:50:05 +0000 [thread overview]
Message-ID: <176910060535.1806518.2169700983805092118.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260122091003.398400-1-hadess@hadess.net>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 22 Jan 2026 10:04:59 +0100 you wrote:
> This supersedes the "Port text docs to RST" patchset
>
> Changes since v2:
> - Move all man pages under doc/ so make it easier to reference
> in the HTML docs.
> - Fix syntax error in maintainer-guidelines
> Changes since v1:
> - Fix distcheck
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/9] doc: Rename section 7 man pages
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=5e2bb7b1ba13
- [BlueZ,v3,2/9] doc: Move all the man pages to doc/
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=44e3dd321e4b
- [BlueZ,v3,3/9] doc: Port assigned-numbers.txt to RST
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e93d8cd4fe41
- [BlueZ,v3,4/9] doc: Port thermometer-api.txt to RST
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=4371db7798b3
- [BlueZ,v3,5/9] doc: Port security-bugs.txt to RST
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=17d407e34cbe
- [BlueZ,v3,6/9] doc: Port coding-style.txt to RST
(no matching commit)
- [BlueZ,v3,7/9] doc: Port sap-api.txt to RST
(no matching commit)
- [BlueZ,v3,8/9] doc: Port maintainer-guidelines.txt to RST
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=fddcda9751af
- [BlueZ,v3,9/9] doc: Port health-api.txt to RST
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-22 16:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:04 [BlueZ v3 0/9] Port text docs to RST and move man pages Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 1/9] doc: Rename section 7 " Bastien Nocera
2026-01-22 10:07 ` Port text docs to RST and move " bluez.test.bot
2026-01-22 9:05 ` [BlueZ v3 2/9] doc: Move all the man pages to doc/ Bastien Nocera
2026-01-22 9:57 ` Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 3/9] doc: Port assigned-numbers.txt to RST Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 4/9] doc: Port thermometer-api.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 5/9] doc: Port security-bugs.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 6/9] doc: Port coding-style.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 7/9] doc: Port sap-api.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 8/9] doc: Port maintainer-guidelines.txt " Bastien Nocera
2026-01-22 9:05 ` [BlueZ v3 9/9] doc: Port health-api.txt " Bastien Nocera
2026-01-22 16:50 ` patchwork-bot+bluetooth [this message]
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=176910060535.1806518.2169700983805092118.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=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