From: "Collin R. Mulliner" <collin@betaversion.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] L2CAP raw socket patch
Date: Wed, 11 Feb 2004 00:07:22 +0100 [thread overview]
Message-ID: <20040211000722.2368d2e9.collin@betaversion.net> (raw)
In-Reply-To: <1076452346.2777.31.camel@pegasus>
Hi All,
so what do you all think about the RAW socket patch, does it make sense
putting it into the official tree?
... Collin
--
Collin Mulliner <collin@betaversion.net>
BATAVERSiON Systems [www.betaversion.net]
Linux is something for Windows haters, BSD something for Unix lovers.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-02-10 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 11:49 [Bluez-devel] L2CAP raw socket patch Collin R. Mulliner
2004-02-10 22:16 ` Marcel Holtmann
[not found] ` <20040210232330.4cf4935d.collin@betaversion.net>
2004-02-10 22:32 ` Marcel Holtmann
2004-02-10 23:07 ` Collin R. Mulliner [this message]
2004-02-22 15:31 ` 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=20040211000722.2368d2e9.collin@betaversion.net \
--to=collin@betaversion.net \
--cc=bluez-devel@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