All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ademar de Souza Reis Jr." <ademar@conectiva.com.br>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Questions about BlueZ in  commercial use
Date: Mon, 28 Jun 2004 10:39:15 -0400	[thread overview]
Message-ID: <40E02D93.8090305@conectiva.com.br> (raw)
In-Reply-To: <20040627125235.GA15938@gmx.net>

Nicholas A. Preyss wrote:
> On  0, KeiHachi <keihachi@swissinfo.org> wrote:
> 
>>I have some questions about BlueZ.
>>
>>Our company is investigating now about BlueZ,
>>to determine whether it is useful to use in our commercial product, or not.
> 
> 
> If this is the first GPL software you are using, please read and 
> understand the implications of this license. This is no offense, but i
> think some DVD and Router manufacturer didn't do this before integrating
> linux code in their products.
> 

Hello.

While we're at this topic: Is there a way to get a license to use the bluez 
code in a comercial, closed-source, product? (I was thinking about something 
like what QT/Trolltech does).

I'm sorry if this has been asked before, but I haven't found it in the 
archives and it's not in the FAQ.

Thanks.

-- 
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

  parent reply	other threads:[~2004-06-28 14:39 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. [this message]
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.
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=40E02D93.8090305@conectiva.com.br \
    --to=ademar@conectiva.com.br \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=nalp@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.