From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Re: adding Additional Protocol Descriptor List
Date: Wed, 14 Dec 2005 08:41:20 +0100 [thread overview]
Message-ID: <1134546080.14885.24.camel@localhost> (raw)
In-Reply-To: <20051214073020.77669.qmail@web32409.mail.mud.yahoo.com>
Hi Arch,
> I have tried writing code to add the Additional Protocol Descriptor
> List. But it seems that the data still cannot be added as a 3-level
> sequence (sequence of a sequence of a sequence). The data I added for
> the Additional Protocol Descriptor List still look similar to the
> Protocol Descriptor List (2-level sequence of data).
you should coordinate with Collin, because he also needs this.
> <
> SPAN style="mso-spacerun: yes">
And please never post HTML emails to the mailing list. The plain old
ASCII emails are still working perfect.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-12-14 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 7:30 [Bluez-users] Re: adding Additional Protocol Descriptor List Arch Sayo
2005-12-14 7:41 ` Marcel Holtmann [this message]
2005-12-14 9:29 ` Marcel Holtmann
2005-12-15 8:35 ` [Bluez-users] just asking oj ravadilla
2005-12-15 8:52 ` Marcel Holtmann
2005-12-20 0:32 ` [Bluez-users] marcel@holtmann.org oj ravadilla
2005-12-20 0:46 ` Marcel Holtmann
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=1134546080.14885.24.camel@localhost \
--to=marcel@holtmann.org \
--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;
as well as URLs for NNTP newsgroup(s).