From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] [PATCH] some manual pages patches
Date: Sun, 04 Jun 2006 15:06:54 +0200 [thread overview]
Message-ID: <1149426414.8053.0.camel@localhost> (raw)
In-Reply-To: <20060603134011.GA13263@esaurito.net>
Hi Filippo,
> the two attached patches for l2ping and pand apply against current CVS.
>
> The pand patch is really easy, it just appends a SCRIPTS section to explain the
> /etc/bluetooth/pan/dev-up usage, it may be worth including it in a file to be
> --included to help2man:
>
> [SCRIPTS]
> pand will execute \fB/etc/bluetooth/pan/dev-up\fR \fIdevice\fR \fIdestination\fR
> when the interface becomes available.
both patches are applied now. Thanks.
> You may want to discard the first chunk of l2ping.1.patch as it changes the
> l2ping section from 1 to 8.
>
> IMO section 8 (system administration commands) is more suitable at least for
> pand,hcid and hidd, being them daemons. The l2ping (for example) case is tricky, on
> a normal system it would require root privileges so it is not really a user
> command.
This is historical and might need to change that, but not right now.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-04 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-03 13:40 [Bluez-devel] [PATCH] some manual pages patches Filippo Giunchedi
2006-06-04 13:06 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-01 18:05 Filippo Giunchedi
2006-06-01 18:38 ` Marcel Holtmann
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=1149426414.8053.0.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).