public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Fw: Next Release, and Device.DiscoverServices
Date: Fri, 20 Jun 2008 05:52:24 +0200	[thread overview]
Message-ID: <1213933944.25820.51.camel@violet> (raw)
In-Reply-To: <046701c8d25f$0dcf13a0$6701a8c0@freqonedev>

Hi David,

> I think I answered my question when I saw the tag for release 3.33
> show up on cvs.bluez.sourceforge.net.
>  
> For now, I have pulled only REL-3_33 and not subsequent patches -- to
> see if this new release answers my questions WRT UUIDs in
> GetProperties, etc., connecting with SSP, and the like.

I did actually answer to your question and mentioned that I will do a
new release the other day.

http://bluez.sf.net/bluez-{libs,utils}-3.33.tar.gz

> I also hope you are successful in getting the bluez.org site back up;
> it must have been a serious problem to take it down for so long...

Harddisk issue and I hoped they fix it soon. Otherwise I really might
have to push it to a different machine.

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://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-06-20  3:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 22:51 [Bluez-devel] Fw: Next Release, and Device.DiscoverServices David Stockwell
2008-06-20  3:52 ` 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=1213933944.25820.51.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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