From: Rahul Tank <gr8rahul@gmail.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Problem while compiling bluez-utils-3.22
Date: Tue, 30 Oct 2007 12:02:45 +0530 [thread overview]
Message-ID: <4726D00D.2020609@gmail.com> (raw)
In-Reply-To: <00c301c81abe$137d8240$832fc70a@dlh.st.com>
Sumeet VERMA wrote:
> Hi Rahul
> I cross checked. It 3.21..sorry for the mistake. Is it fixed in 3.22?
>
>
>
Yes :)
thanks,
rahul
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-10-30 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 5:30 [Bluez-users] Problem while compiling bluez-utils-3.22 Sumeet VERMA
2007-10-30 6:23 ` Rahul Tank
2007-10-30 6:28 ` Sumeet VERMA
2007-10-30 6:32 ` Rahul Tank [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=4726D00D.2020609@gmail.com \
--to=gr8rahul@gmail.com \
--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