public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gollub <dgollub@suse.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] kdebluetooth release 1.0 Beta 3
Date: Wed, 13 Jun 2007 11:31:27 +0200	[thread overview]
Message-ID: <200706131131.27379.dgollub@suse.de> (raw)
In-Reply-To: <200706121149.14306.dgollub@suse.de>

Ooops, forgot  to add the link:

http://sourceforge.net/project/showfiles.php?group_id=89888&package_id=147546&release_id=515234

... and ...

http://bluetooth.kmobiletools.org/1.0-beta3

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-06-13  9:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12  9:49 [Bluez-users] kdebluetooth release 1.0 Beta 3 Daniel Gollub
2007-06-13  9:31 ` Daniel Gollub [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=200706131131.27379.dgollub@suse.de \
    --to=dgollub@suse.de \
    --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