From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Moving towards a new API for BlueZ 4.0
Date: Thu, 20 Mar 2008 11:49:47 -0300 [thread overview]
Message-ID: <20FBD040-B040-43F0-9A1F-E5EF97DA9B85@gmail.com> (raw)
In-Reply-To: <039f01c88a15$a848aaa0$6701a8c0@freqonedev>
Hi David,
On Mar 19, 2008, at 20:04, David Stockwell wrote:
>
> Any interest?
Sure. The current code (mostly written by me) is something rather
quickly put together to get the basic functionality in place.
Especially the metadata transfer would be nice to get implemented
since it's a mandatory feature for category 1 (player/recorder)
devices in version 1.3 of the specification.
> Who should I communicate with?
In addition this list (as Marcel already mentioned) a good place to be
in contact with the developers is the #bluez channel on
irc.freenode.net.
Johan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-03-20 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 20:32 [Bluez-devel] Moving towards a new API for BlueZ 4.0 Marcel Holtmann
2008-03-14 10:23 ` Manuel Naranjo
2008-03-14 12:23 ` Marcel Holtmann
2008-03-14 13:44 ` Manuel Naranjo
2008-03-14 14:00 ` Marcel Holtmann
2008-03-14 14:15 ` Manuel Naranjo
2008-03-14 14:20 ` Robert Rawlins
2008-03-19 23:04 ` David Stockwell
2008-03-20 13:50 ` Marcel Holtmann
2008-03-20 14:49 ` Johan Hedberg [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=20FBD040-B040-43F0-9A1F-E5EF97DA9B85@gmail.com \
--to=johan.hedberg@gmail.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