From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: socket API extensions workgroup at OpenGroup needs HELP
Date: Wed, 20 Feb 2002 17:57:04 -0500 [thread overview]
Message-ID: <200202202257.g1KMv4c04306@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1014244622.20316.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.1014244622.20316.linux-kernel2news@redhat.com>
> Interested people should contact the working group co-chairs for details
> about how to join the effort:
> David Edmondson (david.edmondson@sun.co) or
> Satya Sharma (ssharma@us.ibm.com)
>
> The URL of the OpenGroup Interconnect Software Consortium is:
> http://www.opengroup.org/icsc/
Yea, yea. The little problem here is that TOG is not getting it.
When I see a website that says "Employees of member companies should
send mail to the Consortium Administrator requesting access to the
Member area.", I sure as hell is not getting a hardon about working
on "overtaking Winsock" (and why exactly would we want to copy
broken attempts to embrace and extend? Perhaps you should talk to
a certain <i>monkey lover company</i> about it).
I would not mind to participate in something more open.
If anyone has a suggestion of a mailing list which works
in a way of tcp-implementors, but on the topic of socket API
extensions for Infiniband, then I am interested.
-- Pete
next parent reply other threads:[~2002-02-20 22:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1014244622.20316.linux-kernel2news@redhat.com>
2002-02-20 22:57 ` Pete Zaitcev [this message]
2002-02-20 23:21 ` socket API extensions workgroup at OpenGroup needs HELP Alexander Viro
2002-02-20 23:33 ` Jan Harkes
2002-02-21 0:00 ` Alexander Viro
2002-02-21 0:05 ` Larry McVoy
2002-02-20 23:44 ` Alan Cox
2002-02-21 0:06 ` Larry McVoy
[not found] <200202202257.g1KMv4c04306@devserv.devel.redhat.com.suse.lists.linux.kernel>
[not found] ` <E16dgPr-000595-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-02-21 12:01 ` Andi Kleen
2002-02-20 14:18 Louis Laborde
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=200202202257.g1KMv4c04306@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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