public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: KeiHachi <keihachi@swissinfo.org>
Cc: "Nicholas A. Preyss" <nalp@gmx.net>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Questions about BlueZ in  commercial use
Date: Mon, 28 Jun 2004 19:22:29 +0200	[thread overview]
Message-ID: <1088443349.6030.37.camel@pegasus> (raw)
In-Reply-To: <001701c45d2d$3fe99280$0364a8c0@haruo>

Hi KeiHachi,

> > ..but i am quite sure this might be possible. Marcel while probably
> > reply itself. He is the best suited person, for such a job.
> 
> Yes, I think so, too.
> The problem is whether it is acceptable to ask him to do such a job, or not.
> I'm worried that such a business model may be unseemly in the open-source world.
> (This is the reason why I ask a question to this mailing-list)

you can always ask such a question. In general this is always possible,
but depending on my free time and the amount of money you wanna spend, I
will say yes or no.

> > I personaly wouldn"t use HID or SCO support in a commercial device.
> 
> Why won't you use these features in a commercial device?
> (This is only my personal interest.)

There is still some work to do for a clean implementation. Even if it
works, means not that I will send it for kernel inclusion. My personal
standards for source code are very high. You should really had come to
the LinuxTag and asked me in personal.

Regards

Marcel




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

  reply	other threads:[~2004-06-28 17:22 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 [this message]
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.
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=1088443349.6030.37.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=keihachi@swissinfo.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox