You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@apr.apache.org by fi...@apache.org on 2004/12/11 05:20:43 UTC
svn commit: r111574 - /apr/apr/trunk/file_io/unix/readwrite.c
Author: fielding
Date: Fri Dec 10 20:20:42 2004
New Revision: 111574
URL: http://svn.apache.org/viewcvs?view=rev&rev=111574
Log:
typo in comment
Modified:
apr/apr/trunk/file_io/unix/readwrite.c
Modified: apr/apr/trunk/file_io/unix/readwrite.c
Url: http://svn.apache.org/viewcvs/apr/apr/trunk/file_io/unix/readwrite.c?view=diff&rev=111574&p1=apr/apr/trunk/file_io/unix/readwrite.c&r1=111573&p2=apr/apr/trunk/file_io/unix/readwrite.c&r2=111574
==============================================================================
--- apr/apr/trunk/file_io/unix/readwrite.c (original)
+++ apr/apr/trunk/file_io/unix/readwrite.c Fri Dec 10 20:20:42 2004
@@ -247,7 +247,7 @@
* over the iovec one at a time, we loose the atomic properties of
* writev(). The other option is to combine the entire iovec into one
* buffer that we could then send in one call to write(). This is not
- * reasonable since we do not know how much data an iocev could contain.
+ * reasonable since we do not know how much data an iovec could contain.
*
* The only reasonable option, that maintains the semantics of a real
* writev(), is to only write the first iovec. Callers of file_writev()