From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Tedd Ho-Jeong An <hj.tedd.an@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ v2] monitor: Update manpage
Date: Fri, 30 Apr 2021 09:30:05 +0200 [thread overview]
Message-ID: <F0707FBF-6B60-40E2-9254-72658E2BC60E@holtmann.org> (raw)
In-Reply-To: <CABBYNZJJHLZdhOFHrTHV7XN7++t4XKq3yHxS2wsi2bJ2AkRnVw@mail.gmail.com>
Hi Luiz,
>> This patch updates the manpage for btmon written in rst format.
>> ---
>> Makefile.am | 26 ++++---
>> Makefile.tools | 4 ++
>> configure.ac | 4 ++
>> doc/btmon.txt | 35 ----------
>> monitor/btmon.rst | 172 ++++++++++++++++++++++++++++++++++++++++++++++
>
> I do wonder why you change the location from doc to monitor, I think
> we actually should keep all the documentation under doc and perhaps
> even have a dedicated make target for those since we would likely want
> to generate all the manpages from rst which may be time consuming so
> people not interested on it can just skip it.
in iwd, we moved all the manual pages next to the source of the daemon/tools. So yes, I would put this into monitor directory as well.
Regards
Marcel
next prev parent reply other threads:[~2021-04-30 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 6:22 [BlueZ v2] monitor: Update manpage Tedd Ho-Jeong An
2021-04-28 6:48 ` [BlueZ,v2] " bluez.test.bot
2021-04-30 3:51 ` [BlueZ v2] " Luiz Augusto von Dentz
2021-04-30 7:30 ` Marcel Holtmann [this message]
2021-04-30 21:43 ` Tedd Ho-Jeong An
2021-04-30 22:41 ` Luiz Augusto von Dentz
2021-05-01 1:59 ` Marcel Holtmann
2021-05-01 3:22 ` Tedd Ho-Jeong An
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=F0707FBF-6B60-40E2-9254-72658E2BC60E@holtmann.org \
--to=marcel@holtmann.org \
--cc=hj.tedd.an@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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.