From: "Niels v/d Spek" <gmaneBluez@lumensoft.nl>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Concept implementation: (still to be named)newipc.h
Date: Thu, 11 Oct 2007 14:25:49 +0200 [thread overview]
Message-ID: <fel4pf$act$1@sea.gmane.org> (raw)
In-Reply-To: 470E0D3E.8030104@free.fr
Hello,
I'm a newby ad all this stuff and like to work with the Headset profile
sometime in the future.
Reading your header file i got some questions.
>> * License as published by the Free Software Foundation; either
>> * version 2.1 of the License, or (at your option) any later version.
This i see on more places, but i do not understand why you give the user the
posiblity to use a newer version then the 2.1? Isn't it posible that newerer
version can give someone the right's to use it commercial or give the rights
that you totally not want to happen?
>> Message sequence chart of streaming sequence for A2DP transport
Is see only the A2DP ttransport do you make also a SCO transport libery?
Thanks
Niels
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-10-11 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 21:33 Concept implementation: (still to be named) newipc.h Fabien Chevalier
2007-10-11 11:47 ` Fabien Chevalier
2007-10-11 12:25 ` Niels v/d Spek [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='fel4pf$act$1@sea.gmane.org' \
--to=gmanebluez@lumensoft.nl \
--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