aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorkazu <kazu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2011-05-07 10:47:23 +0000
committerkazu <kazu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2011-05-07 10:47:23 +0000
commit68417aa5ce4e6608da1304dac49dda42503031bf (patch)
tree143f95507a917de986b81c7ab9bad46721049180
parent1bd2c78b05b05f7868cd3b5bfc1e02ae11fb9eaf (diff)
downloadruby-68417aa5ce4e6608da1304dac49dda42503031bf.tar.gz
fix typos
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@31463 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-rw-r--r--ChangeLog4
1 files changed, 2 insertions, 2 deletions
diff --git a/ChangeLog b/ChangeLog
index f766c11273..f6c9c03ef6 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -9,7 +9,7 @@ Sat May 7 15:18:06 2011 KOSAKI Motohiro <kosaki.motohiro@gmail.com>
fix incorrect native_cond_signal call when deadlock was detected.
* thread.c (lock_func): timedwait don't touch cond_waiting and
- cond_notifid variables.
+ cond_notified variables.
Sat May 7 15:15:10 2011 KOSAKI Motohiro <kosaki.motohiro@gmail.com>
@@ -116,7 +116,7 @@ Fri May 6 15:01:11 2011 URABE Shyouhei <shyouhei@ruby-lang.org>
is a wrong idea because when using alloca there is always risk
of integer overflow. A function that accepts outer-process
resources like this should not blindly trust its inputs. In
- this particular case we just want to generate miliseconds
+ this particular case we just want to generate milliseconds
resolution by strtod() so the string in question needs no more
length than what we originally have. Ignoring lesser
significant digits should suffice I believe.