From: gcagasan@lexmark.com
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] BlueZ licensing inquiry
Date: Tue, 29 Mar 2005 13:23:12 +0800 [thread overview]
Message-ID: <OF200FCC20.5703443A-ON48256FD3.001D7002-48256FD3.001DBAF3@lexmark.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 206 bytes --]
I would like to know, what is the licensing for BlueZ? Are there any
issues from a legal or licensing stand-point if we port it to another OS?
thanks,
Gail Cagasan
Lexmark Research and Development Corp.
[-- Attachment #2: Type: text/html, Size: 387 bytes --]
next reply other threads:[~2005-03-29 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 5:23 gcagasan [this message]
2005-03-29 5:36 ` [Bluez-users] BlueZ licensing inquiry Michal Semler
2005-03-29 5:44 ` 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=OF200FCC20.5703443A-ON48256FD3.001D7002-48256FD3.001DBAF3@lexmark.com \
--to=gcagasan@lexmark.com \
--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