From 1ff9d18d398fb9f35b72fa0174048e1f36ec5020 Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Fri, 29 Nov 2013 11:07:43 -0600 Subject: [PATCH 1/2] Removed use of gendered pronoun --- src/unix/fs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/unix/fs.c b/src/unix/fs.c index 64517c4652..4e572b7d96 100644 --- a/src/unix/fs.c +++ b/src/unix/fs.c @@ -313,7 +313,7 @@ static ssize_t uv__fs_sendfile_emul(uv_fs_t* req) { * * 1. Read errors are reported only if nsent==0, otherwise we return nsent. * The user needs to know that some data has already been sent, to stop - * him from sending it twice. + * them from sending it twice. * * 2. Write errors are always reported. Write errors are bad because they * mean data loss: we've read data but now we can't write it out. From 587609b4dd96d6f34c8ae27d4040f59f287b2313 Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Fri, 29 Nov 2013 15:11:24 -0600 Subject: [PATCH 2/2] Replaced gendered language in a comment --- src/unix/stream.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/unix/stream.c b/src/unix/stream.c index 5b8d15ec03..8fa8066eab 100644 --- a/src/unix/stream.c +++ b/src/unix/stream.c @@ -668,8 +668,8 @@ static void uv__write_req_finish(uv_write_t* req) { /* Only free when there was no error. On error, we touch up write_queue_size * right before making the callback. The reason we don't do that right away * is that a write_queue_size > 0 is our only way to signal to the user that - * he should stop writing - which he should if we got an error. Something to - * revisit in future revisions of the libuv API. + * they should stop writing - which they should if we got an error. Something + * to revisit in future revisions of the libuv API. */ if (req->error == 0) { if (req->bufs != req->bufsml)