public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Christoph Bartelmus <bluez-users@bartelmus.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] License of BlueZ libraries
Date: Tue, 24 Feb 2004 17:14:29 +0100	[thread overview]
Message-ID: <1077639268.2919.4.camel@pegasus> (raw)
In-Reply-To: <93S9$6GSqpB@bartelmus.de>

Hi Christoph,

> this question has been already asked a while ago with no definite answer
> (http://sourceforge.net/mailarchive/message.php?msg_id=2435632).
> 
> Are there any plans to release the Bluez user-space libraries under LGPL?

for the current version of the libraries I have no plan to release them
under LGPL, but the new libs2 should be LGPL from the start. There are
some critical parts where the copyright still belongs to Qualcomm. For
me there is no problem to make libs2 LGPL, but I need confirmation from
Max and from Qualcomm for a final LGPL version.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-02-24 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 15:31 [Bluez-users] License of BlueZ libraries Christoph Bartelmus
2004-02-24 16:14 ` 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=1077639268.2919.4.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@bartelmus.de \
    --cc=bluez-users@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