From: Marcel Holtmann <marcel@holtmann.org>
To: Edouard Lafargue <ELafargue@montrouge.sns.slb.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Documentation for hcid.conf ?
Date: Tue, 23 Mar 2004 16:04:17 +0100 [thread overview]
Message-ID: <1080054257.2515.23.camel@pegasus> (raw)
In-Reply-To: <1080053029.7507.40.camel@gryffindor>
Hi Edouard,
> Below is my effort at describing the role/effect of the "class"
> option, please feel free to include this in the "hcid.conf" man page
> -does it exist ? It's really needed!-. I would appreciate if someone
> who is more knowledgeable than me in this field could look at this and
> correct what I'm saying there.
very nice. The job of the documentation maintainer is still open ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-03-23 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 14:43 [Bluez-devel] Documentation for hcid.conf ? Edouard Lafargue
2004-03-23 15:04 ` Marcel Holtmann [this message]
[not found] ` <1080059454.7507.85.camel@gryffindor>
2004-03-23 17:29 ` Marcel Holtmann
2004-03-24 22:23 ` Fredrik Noring
2004-03-23 17:38 ` Collin R. Mulliner
2004-03-23 17:48 ` Marcel Holtmann
2004-03-23 18:31 ` Edouard Lafargue
[not found] ` <20040323225438.6b7bb3ee@coredump>
2004-03-23 22:36 ` 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=1080054257.2515.23.camel@pegasus \
--to=marcel@holtmann.org \
--cc=ELafargue@montrouge.sns.slb.com \
--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