From: Vladimir Botka <vbotka@gmail.com>
To: Ivan Baidakou <the.dmol@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: dund
Date: Sun, 12 Sep 2010 16:37:14 +0200 [thread overview]
Message-ID: <20100912163714.09aac1e3@vaio.site> (raw)
In-Reply-To: <20100912114411.2678ffbe@gmail.com>
On Sun, 12 Sep 2010 11:44:11 +0300
Ivan Baidakou <the.dmol@gmail.com> wrote:
> You haven't real experience, right?
I have.
# pilot-xfer -p bt:00:07:E0:B3:DD:03 -l
Listening for incoming connection on bt:00:07:E0:B3:DD:03... connected!
Reading list of databases in RAM...
AdditDVSData
ADD050SData
AdditSystemSData
<snip>
Cheers,
-vlado
next prev parent reply other threads:[~2010-09-12 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 18:45 dund Ivan Baidakou
2010-09-11 23:26 ` dund Bastien Nocera
2010-09-12 8:44 ` dund Ivan Baidakou
2010-09-12 14:37 ` Vladimir Botka [this message]
2010-09-12 14:45 ` dund Bastien Nocera
2010-09-13 20:47 ` dund Ivan Baidakou
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=20100912163714.09aac1e3@vaio.site \
--to=vbotka@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=the.dmol@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).