From: David Miller <davem@davemloft.net>
To: drepper@redhat.com
Cc: johnpol@2ka.mipt.ru, netdev@vger.kernel.org, alan@redhat.com
Subject: Re: bind and O_NONBLOCK
Date: Sat, 22 Sep 2007 22:58:18 -0700 (PDT) [thread overview]
Message-ID: <20070922.225818.74741259.davem@davemloft.net> (raw)
In-Reply-To: <46F54CA5.8020200@redhat.com>
From: Ulrich Drepper <drepper@redhat.com>
Date: Sat, 22 Sep 2007 10:11:01 -0700
> There was no public mail. I asked RH engineering for proposals for
> changes to the POSIX spec and Alan replied.
Please do not discuss such proposals only privately, especially when
the ramifications affect the entire community.
It is important the things get hashed out on a public forum where
all networking developers can add their insight into the problem.
next prev parent reply other threads:[~2007-09-23 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 5:59 bind and O_NONBLOCK Ulrich Drepper
2007-09-22 16:14 ` Evgeniy Polyakov
2007-09-22 16:21 ` Ulrich Drepper
2007-09-22 16:59 ` Evgeniy Polyakov
2007-09-22 17:11 ` Ulrich Drepper
2007-09-22 17:19 ` Evgeniy Polyakov
2007-09-23 5:58 ` David Miller [this message]
2007-09-23 20:43 ` Alan Cox
2007-09-22 17:35 ` Alan Cox
2007-09-22 17:40 ` Evgeniy Polyakov
2007-09-28 22:56 ` David Miller
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=20070922.225818.74741259.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alan@redhat.com \
--cc=drepper@redhat.com \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).