public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Recent bluez-gnome problems
Date: Wed, 2 Apr 2008 21:50:28 +0200	[thread overview]
Message-ID: <2218E26D-54B0-47BF-AC87-7DFE9927EFE2@holtmann.org> (raw)
In-Reply-To: <89b6ba3a0804021244q2bd22bdeo5d774a6901426032@mail.gmail.com>

Hi Patryk,

>> it is actually our fault within bluez-utils-3.29. We accidently
>> removed the device discover calls from the API. Expect a new release
>> soon.
>
> Hi guys, any news on this front? Is there an already planned release?
> If not, what is the safe version to revert to in the distro?

I am doing the release today. Using 3.28 will be good. Or you grab  
that one patch from the CVS. It is something like changing two or  
three lines of code.

Regards

Marcel


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2008-04-02 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 22:40 [Bluez-users] Recent bluez-gnome problems Patryk Zawadzki
2008-03-26 16:29 ` Marcel Holtmann
2008-03-26 16:37   ` Patryk Zawadzki
2008-03-26 16:40     ` Marcel Holtmann
2008-03-27 19:29       ` Patryk Zawadzki
2008-03-27 23:15         ` Marcel Holtmann
2008-04-02 19:44           ` Patryk Zawadzki
2008-04-02 19:50             ` Marcel Holtmann [this message]

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=2218E26D-54B0-47BF-AC87-7DFE9927EFE2@holtmann.org \
    --to=marcel@holtmann.org \
    --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