From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
In-Reply-To: <57c68ddc0703050126n2696b8a7h7a4d36f605e6d2cc@mail.gmail.com>
References: <57c68ddc0702282245x777b63e0la3156781ed55804f@mail.gmail.com>
	<1172921500.24446.10.camel@aeonflux.holtmann.net>
	<57c68ddc0703050126n2696b8a7h7a4d36f605e6d2cc@mail.gmail.com>
Date: Mon, 05 Mar 2007 13:50:27 +0100
Message-Id: <1173099028.6638.21.camel@aeonflux.holtmann.net>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] rfcomm channel and ioctl
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: text/plain; charset="us-ascii"
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net

Hi Siddhant,

>           Thanks very much for the reply ... rfcomm sockets are
> working perfectly .... rctest.c  example really eased out the things
> for me. 
> 
>            I would like to contribute for the bluez development , if
> thats possible please suggest ways in which i can do that , may be for
> the start i can fix small bugs with known solution. 

go ahead and start working on things. Post whatever you have to the
mailing list for review.

Regards

Marcel


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel