From: Davide Libenzi <davidel@xmailserver.org>
To: Dan Kegel <dkegel@ixiacom.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: re: epoll patches queue status and glibc submission ...
Date: Wed, 27 Nov 2002 12:56:38 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.50.0211271255580.1827-100000@blue1.dev.mcafeelabs.com> (raw)
In-Reply-To: <3DE52FC7.1050405@ixiacom.com>
On Wed, 27 Nov 2002, Dan Kegel wrote:
> Hi Davide,
> I just realized that 'edge triggered I/O readiness notification facility'
> is too jargony. A plain English wording of the man page title might be
>
> epoll \- I/O readiness change notification facility
>
> This is shorter and much clearer. Apologies for having suggested
> the earlier jargony text.
Ok, done. Any other crappyness at your sight ?
- Davide
next prev parent reply other threads:[~2002-11-27 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 20:49 Dan Kegel
2002-11-27 20:56 ` Davide Libenzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 20:09 Davide Libenzi
2002-11-27 21:25 ` Chris Friesen
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=Pine.LNX.4.50.0211271255580.1827-100000@blue1.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=dkegel@ixiacom.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
all inboxes | Powered by JetHome®