From: "Ademar de Souza Reis Jr." <ademar@conectiva.com.br>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Questions about BlueZ in commercial use
Date: Mon, 28 Jun 2004 13:06:18 -0400 [thread overview]
Message-ID: <40E0500A.6080001@conectiva.com.br> (raw)
In-Reply-To: <1088437134.6030.7.camel@pegasus>
Marcel Holtmann wrote:
> Hi Ademar,
>
>
>>>For the BlueZ library and the utilities we can talk about it. Some time
>>>ago people asked for a LGPL version of the library and actually I tend
>>>to agree with that. However this can't be decided by me alone, because
>>>part of the code is copyright by Qualcomm and also by Maxim Krasnyansky
>>>himself.
>>
>>That would be something really interesting to hear about and I guess it's
>>important to define as soon as possible (to avoid including more people with
>>copyright code in the ring, for example).
>
>
> start asking Max about it. Since he is still working for Qualcomm we may
> resolve this issue very soon. If Qualcomm and Max agree on LGPL for the
> library I will also agree on it.
Added him to CC: just in case he is not following the thread.
Max, could you give us your view about that?
Thanks and best regards,
- Ademar
--
Ademar de Souza Reis Jr. <ademar@conectiva.com.br>
Conectiva S.A. - http://www.conectiva.com.br
^[:wq!
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-06-28 17:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 9:47 [Bluez-devel] Questions about BlueZ in commercial use KeiHachi
2004-06-27 12:52 ` Nicholas A. Preyss
2004-06-27 14:45 ` KeiHachi
2004-06-27 17:13 ` Nicholas A. Preyss
2004-06-28 16:30 ` KeiHachi
2004-06-28 17:22 ` Marcel Holtmann
2004-06-27 18:29 ` Marcel Holtmann
2004-06-28 16:33 ` KeiHachi
2004-06-28 17:45 ` Marcel Holtmann
2004-06-28 14:39 ` Ademar de Souza Reis Jr.
2004-06-28 14:48 ` Marcel Holtmann
2004-06-28 15:19 ` Ademar de Souza Reis Jr.
2004-06-28 15:38 ` Marcel Holtmann
2004-06-28 15:59 ` Stephen Crane
2004-06-28 17:06 ` Ademar de Souza Reis Jr. [this message]
2004-06-28 17:15 ` Marcel Holtmann
2004-06-27 18:09 ` Marcel Holtmann
2004-06-27 19:10 ` Nicholas A. Preyss
2004-06-27 19:09 ` Marcel Holtmann
2004-06-27 20:34 ` Nicholas A. Preyss
2004-06-27 20:49 ` Marcel Holtmann
2004-06-27 21:42 ` Nicholas A. Preyss
2004-06-28 7:37 ` Marcel Holtmann
2004-06-28 16:28 ` KeiHachi
2004-06-28 17:13 ` Marcel Holtmann
2004-06-29 17:08 ` KeiHachi
2004-06-29 17:41 ` Marcel Holtmann
2004-06-30 16:22 ` KeiHachi
2004-06-30 18:11 ` Marcel Holtmann
2004-07-04 8:57 ` KeiHachi
2004-07-04 11:38 ` Marcel Holtmann
2004-07-04 13:19 ` Peter Favrholdt
2004-07-04 13:47 ` 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=40E0500A.6080001@conectiva.com.br \
--to=ademar@conectiva.com.br \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.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