From: Eric Wong <e@80x24.org>
To: yahns-public@yhbt.net
Subject: [PATCH] wbuf: fix typo in bug check for sendfile gem
Date: Tue, 1 Dec 2015 03:21:30 +0000 [thread overview]
Message-ID: <20151201032130.13496-1-e@80x24.org> (raw)
This typo would've only be triggered if the sendfile gem itself
turns out to be buggy and returns an undocumented return code.
---
lib/yahns/wbuf.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/yahns/wbuf.rb b/lib/yahns/wbuf.rb
index 9888a8c..1a24aab 100644
--- a/lib/yahns/wbuf.rb
+++ b/lib/yahns/wbuf.rb
@@ -71,7 +71,7 @@ class Yahns::Wbuf # :nodoc:
@busy = rv
return rv
else
- raise "BUG: #{rv.nil ? "EOF" : rv.inspect} on tmpio " \
+ raise "BUG: #{rv.nil? ? "EOF" : rv.inspect} on tmpio " \
"sf_offset=#@sf_offset sf_count=#@sf_count"
end while @sf_count > 0
--
EW
reply other threads:[~2015-12-01 3:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: http://yhbt.net/yahns/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151201032130.13496-1-e@80x24.org \
--to=e@80x24.org \
--cc=yahns-public@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
http://yhbt.net/yahns.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).