1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix typos

Browse Source 
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@31463 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
kazu 2011-05-07 10:47:23 +00:00
parent 1bd2c78b05
commit 68417aa5ce
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -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.