From: Marcel Holtmann <marcel@holtmann.org>
To: Onur Safak <linuxbluez@yahoo.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] about the list
Date: Tue, 06 Jul 2004 12:38:23 +0200 [thread overview]
Message-ID: <1089110303.4504.130.camel@pegasus> (raw)
In-Reply-To: <20040706103225.27303.qmail@web90006.mail.scd.yahoo.com>
Hi Onur,
> Bluetooth is a new area to me, which I need to make an application on.
> Currently, I don't have necessary hardware / software set up. I'm
> collecting information from documentations and articles, and so the
> lists are important to me.
>
> First of all, I need to know one thing; is this list for 'developers
> who work with Bluez' or only for 'developers who develop the Bluez
> code'. I've read the archive, but the topics look similar with users'
> list.
the bluez-users list is for people who having problems with using BlueZ
and the bluez-devel mailing list is for the core developers, but also
for people who wanna start develop applications using BlueZ.
I have an eye on both list, so use that one that you think fits better.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-07-06 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 10:32 [Bluez-devel] about the list Onur Safak
2004-07-06 10:38 ` Marcel Holtmann [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=1089110303.4504.130.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linuxbluez@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox