diff options
author | root <root> | 2007-12-21 05:10:01 +0000 |
---|---|---|
committer | root <root> | 2007-12-21 05:10:01 +0000 |
commit | 5c23f3932f8060a6541f2374689c96c92da21355 (patch) | |
tree | 0412ff4cd8e5064f52628abe210721c17cbd0b7b | |
parent | ed54de67c9823483cc94f0decfd2f5405a5844f7 (diff) |
*** empty log message ***
-rw-r--r-- | ev.3 | 4 | ||||
-rw-r--r-- | ev.pod | 2 |
2 files changed, 3 insertions, 3 deletions
@@ -1107,8 +1107,8 @@ This is how one would do it normally anyway, the important point is that the libev application should not optimise around libev but should leave optimisations to libev. .PP -\fIThs special problem of dup'ed file descriptors\fR -.IX Subsection "Ths special problem of dup'ed file descriptors" +\fIThe special problem of dup'ed file descriptors\fR +.IX Subsection "The special problem of dup'ed file descriptors" .PP Some backends (e.g. epoll), cannot register events for file descriptors, but only events for the underlying file descriptions. That menas when you @@ -951,7 +951,7 @@ This is how one would do it normally anyway, the important point is that the libev application should not optimise around libev but should leave optimisations to libev. -=head3 Ths special problem of dup'ed file descriptors +=head3 The special problem of dup'ed file descriptors Some backends (e.g. epoll), cannot register events for file descriptors, but only events for the underlying file descriptions. That menas when you |