All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Edd Dumbill <edd@usefulinc.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	Max Krasnyansky <maxk@qualcomm.com>,
	Stephen Crane <steve.crane@rococosoft.com>
Subject: [Bluez-users] Re: Release of new BlueZ libs and utils
Date: Fri, 02 Jan 2004 12:04:25 +0100	[thread overview]
Message-ID: <1073041465.25261.21.camel@pegasus> (raw)
In-Reply-To: <1072989541.2634.154.camel@saag>

Hi Edd,

> > For the BlueZ libs I don't plan another release, because the new major
> > version of the Bluetooth library is making good progress. But for the
> > BlueZ Utils I want to make another release that addresses the problems
> > with the pin_helper program. I think the C based bluez-pin is a good
> > idea and maybe we should also integrate the DBus support into the next
> > release. So I like to get comments on this and if you have patches,
> > please resend them.
> 
> For a while now the Debian packages have brought in the DBUS/GTK
> bluez-pin implementation as the default, and I've had no complaints at
> all. DBUS seems to be really catching on as the way to do things like
> this.

I am looking forward to include the bluez-pin as default pin-helper
program. Do you have included the DBUS patch for hcid? If yes, please
mail me the version you have used.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-01-02 11:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 23:55 [Bluez-users] Release of new BlueZ libs and utils Marcel Holtmann
2003-12-19  0:28 ` Michal Semler (volny.cz)
2003-12-19  9:19   ` Marcel Holtmann
2003-12-19 10:22     ` Michal Semler (volny.cz)
2003-12-20  7:14       ` Charles Bueche
2003-12-20 14:39         ` Marcel Holtmann
2003-12-19 10:15 ` Stephen Crane
2004-01-01 20:39 ` Edd Dumbill
2004-01-02 11:04   ` Marcel Holtmann [this message]
2004-01-02 11:09     ` Edd Dumbill
2004-01-02 11:24       ` [Bluez-users] " Marcel Holtmann
2004-01-02 17:18         ` Michal Semler (volny.cz)
2004-01-02 23:35           ` Marcel Holtmann
2004-01-03 19:54             ` Michal Semler (volny.cz)
2004-01-04 10:35               ` Marcel Holtmann
2004-01-03 16:32 ` [Bluez-users] " Edd Dumbill
2004-01-03 16:47   ` Edd Dumbill
2004-01-03 17:10     ` Marcel Holtmann
2004-01-03 18:33       ` Edd Dumbill
2004-01-04 10:38         ` Marcel Holtmann
2004-01-06 11:26           ` Edd Dumbill
2004-01-06 12:37             ` Marcel Holtmann
2004-01-06 13:11               ` Edd Dumbill
2004-01-06 13:20                 ` Marcel Holtmann
2004-01-06 14:02                   ` Edd Dumbill
2004-01-06 14:15                     ` Marcel Holtmann
2004-01-06 14:30                       ` Edd Dumbill
2004-01-06 14:18                     ` Xavier Garreau
2004-01-06 12:54             ` Xavier Garreau
2004-01-06 13:06               ` 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=1073041465.25261.21.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=edd@usefulinc.com \
    --cc=maxk@qualcomm.com \
    --cc=steve.crane@rococosoft.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 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.