From: Szymon Janc <szymon.janc@tieto.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
"Frédéric Danis" <frederic.danis@linux.intel.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH v2 0/7] Move adapter config file to ini-file format
Date: Wed, 10 Oct 2012 15:01:40 +0200 [thread overview]
Message-ID: <3043065.CnC5bYlbBs@uw000953> (raw)
In-Reply-To: <CAJdJm_OCcpXD7oPMQec-Z_UdhF7tfEOCs47Zfrq6+JQVrga2mQ@mail.gmail.com>
Hi,
On Wednesday 10 of October 2012 13:37:33 Anderson Lizardo wrote:
> Hi Marcel,
>
> On Wed, Oct 10, 2012 at 6:03 AM, Marcel Holtmann <marcel@holtmann.org> wrote:
> > For the actual change to the new format, can you first create a document
> > describing the new format. Something like doc/settings-storage.txt or
> > similar (if anyone can think of a better name).
>
> Would be interesting to update ./src/bluetoothd.8.in as well, or
> simply drop the description for config storage files?
I don't think man page should contain such information as description of data
stored by bluetoothd. This is a private daemon data that is not suppose to
be modified by hand.
Instead, it should contain comprehensive information about configuration files
located in /etc/bluetooth and note about location and purpose of data files.
(opposite to what is now in bluetoothd manual..)
By comprehensive I mean not necessarily full description of every option
possible (this could be located in separate manual or in example config files
as it is now) but clear description of what each file is responsible for, when
and how it is parsed etc.
--
BR
Szymon Janc
next prev parent reply other threads:[~2012-10-10 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 8:58 [PATCH v2 0/7] Move adapter config file to ini-file format Frédéric Danis
2012-10-10 8:58 ` [PATCH v2 1/7] adapter: Read name in storage at init Frédéric Danis
2012-10-10 9:57 ` Marcel Holtmann
2012-10-10 8:58 ` [PATCH v2 2/7] adapter: Read device class " Frédéric Danis
2012-10-10 8:58 ` [PATCH v2 3/7] adapter: Move pairable read to load_config() Frédéric Danis
2012-10-10 8:58 ` [PATCH v2 4/7] adapter: Read pairable timeout in storage at init Frédéric Danis
2012-10-10 8:58 ` [PATCH v2 5/7] adapter: Read discoverable " Frédéric Danis
2012-10-10 8:58 ` [PATCH v2 6/7] adapter: Read mode " Frédéric Danis
2012-10-10 8:58 ` [PATCH v2 7/7] adapter: Move saved config to ini-file format Frédéric Danis
2012-10-10 10:00 ` Marcel Holtmann
2012-10-10 10:03 ` [PATCH v2 0/7] Move adapter config file " Marcel Holtmann
2012-10-10 10:37 ` Anderson Lizardo
2012-10-10 13:01 ` Szymon Janc [this message]
2012-10-10 13:33 ` Johan Hedberg
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=3043065.CnC5bYlbBs@uw000953 \
--to=szymon.janc@tieto.com \
--cc=anderson.lizardo@openbossa.org \
--cc=frederic.danis@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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