linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edd Dumbill <edd@usefulinc.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
	Max Krasnyansky <maxk@qualcomm.com>,
	Stephen Crane <steve.crane@rococosoft.com>
Subject: Re: Release of new BlueZ libs and utils
Date: Thu, 01 Jan 2004 20:39:02 +0000	[thread overview]
Message-ID: <1072989541.2634.154.camel@saag> (raw)
In-Reply-To: <1071791711.6635.18.camel@pegasus>

On Thu, 2003-12-18 at 23:55, Marcel Holtmann wrote:
> Hi Folks,
> 
> I don't wanna make big words about it, but after 8 months there are new
> releases of the BlueZ libs and utils packages.

I just uploaded these to Debian sid.  Sorry for the delay, but the
holiday season and the recent Debian break-in delayed me.

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

-- Edd

  parent reply	other threads:[~2004-01-01 20:39 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 [this message]
2004-01-02 11:04   ` [Bluez-users] " Marcel Holtmann
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=1072989541.2634.154.camel@saag \
    --to=edd@usefulinc.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).