[#62297] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap. — Eric Wong <normalperson@...>
nari@ruby-lang.org wrote:
7 messages
2014/05/02
[#62307] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— SASADA Koichi <ko1@...>
2014/05/03
(2014/05/03 4:41), Eric Wong wrote:
[#62402] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— Eric Wong <normalperson@...>
2014/05/05
SASADA Koichi <ko1@atdot.net> wrote:
[#62523] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — ko1@...
Issue #9632 has been updated by Koichi Sasada.
3 messages
2014/05/11
[#62556] doxygen (Re: Re: [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan) — Tanaka Akira <akr@...>
2014-05-11 8:50 GMT+09:00 Eric Wong <normalperson@yhbt.net>:
3 messages
2014/05/13
[#62727] [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl — Eric Wong <normalperson@...>
rb_unlink_method_entry may cause old_me to be swept before the new
7 messages
2014/05/24
[#63039] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/10
Hi,
[#63077] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/10
SASADA Koichi <ko1@atdot.net> wrote:
[#63086] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/11
(2014/06/11 4:47), Eric Wong wrote:
[#63087] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/11
SASADA Koichi <ko1@atdot.net> wrote:
[#62862] [RFC] README.EXT: document rb_gc_register_mark_object — Eric Wong <normalperson@...>
Any comment on officially supporting this as part of the C API?
5 messages
2014/05/30
[ruby-core:62572] 1.9.3-p546 release
From:
Zachary Scott <e@...>
Date:
2014-05-14 02:57:10 UTC
List:
ruby-core #62572
A critical regression was found after the release of 1.9.3-p545[1]. We=E2=80=99d like a release of p546, which includes r45485[2]. In the original announcement for p545[1], it states: > It means that Ruby 1.9.3 goes =E2=80=A6 **never be released unless any cr= itical regressions or security issues are found.** Also, in ruby-core:60503[3] @unak states: > After the last usual release, we will not fix any bugs except urgent secu= rity problems, in principle. Patch 546 is resolves a critical issue which breaks older versions of OpenS= SL, which are still supported by Heroku. This includes anyone using Ubuntu = 10.04 LTS which packages this version of OpenSSL. Please clarify that @unak is still maintainer of 1.9.3, and available to do= the release. From my understanding this requires ci to be green, but since= this is a regression from a security fix the ci was already red to begin w= ith. 1: https://www.ruby-lang.org/en/news/2014/02/24/ruby-1-9-3-p545-is-released= / 2: https://github.com/ruby/ruby/commit/680d09b 3: http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/60503