From: "Daniele Primon" <ledebass@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] SCO flow control patch
Date: Fri, 28 Dec 2007 11:25:45 +0000 [thread overview]
Message-ID: <38687c4a0712280325i7c83701fh838740ec87f04c01@mail.gmail.com> (raw)
In-Reply-To: <E1J86fW-0002SG-KO@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 716 bytes --]
2007/12/28, Brian Sammon <bluez-users@brisammon.fastmail.fm>:
>
> In my readings I've seen a reference to a "SCO flow control patch".
> What is it?
> Where is it?
> Do I need it?
please specify your sourngces. What are those reading? What is the patch
about?
Have you got your configuration working?
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 1380 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-12-28 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 4:17 [Bluez-users] SCO flow control patch Brian Sammon
2007-12-28 11:25 ` Daniele Primon [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=38687c4a0712280325i7c83701fh838740ec87f04c01@mail.gmail.com \
--to=ledebass@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