[#59462] [ruby-trunk - Bug #9342][Open] [PATCH] SizedQueue#clear does not notify waiting threads in Ruby 1.9.3 — "jsc (Justin Collins)" <redmine@...>

9 messages 2014/01/02

[#59466] [ruby-trunk - Bug #9343][Open] [PATCH] SizedQueue#max= wakes up waiters properly — "normalperson (Eric Wong)" <normalperson@...>

11 messages 2014/01/02

[#59498] [ruby-trunk - Bug #9352][Open] [BUG] rb_sys_fail_str(connect(2) for [fe80::1%lo0]:3000) - errno == 0 — "kain (Claudio Poli)" <claudio@...>

10 messages 2014/01/03

[#59516] [ruby-trunk - Bug #9356][Open] TCPSocket.new does not seem to handle INTR — "charliesome (Charlie Somerville)" <charliesome@...>

48 messages 2014/01/03

[#59538] [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — "shyouhei (Shyouhei Urabe)" <shyouhei@...>

33 messages 2014/01/03
[#59582] Re: [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — SASADA Koichi <ko1@...> 2014/01/06

Intersting challenge.

[#59541] Re: [ruby-trunk - Feature #9362][Assigned] Minimize cache misshit to gain optimal speed — Eric Wong <normalperson@...> 2014/01/04

Hi, I noticed a trivial typo in array.c, and it fails building struct.c

[#59583] [ruby-trunk - Bug #9367][Open] REXML::XmlDecl doesn't use user specified quotes — "bearmini (Takashi Oguma)" <bear.mini@...>

12 messages 2014/01/06

[#59642] [ruby-trunk - Bug #9384][Open] Segfault in ruby 2.1.0p0 — "cbliard (Christophe Bliard)" <christophe.bliard@...>

11 messages 2014/01/08

[#59791] About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...>

A while ago I created a proof-of-concept that I intended to use in my

16 messages 2014/01/15
[#59794] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/15

On 15 Jan 2014, at 11:58, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[#59808] Re: About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2014/01/16

Em 15-01-2014 19:42, Eric Hodel escreveu:

[#59810] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/16

On 16 Jan 2014, at 02:15, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[#59826] Re: About unmarshallable DRb objects life-time — Rodrigo Rosenfeld Rosas <rr.rosas@...> 2014/01/17

Em 16-01-2014 19:43, Eric Hodel escreveu:

[#59832] Re: About unmarshallable DRb objects life-time — Eric Hodel <drbrain@...7.net> 2014/01/17

On 17 Jan 2014, at 04:22, Rodrigo Rosenfeld Rosas <rr.rosas@gmail.com> wrote:

[ruby-core:59954] [ruby-trunk - misc #9438] Implementation naming

From: duerst@...
Date: 2014-01-22 03:21:58 UTC
List: ruby-core #59954
Issue #9438 has been updated by Martin D端rst.


 A certain amount of streamlining is certainly a good thing, but we 
 should be aware that people use both "CRuby" and "MRI", often 
 indifferently. We should make sure that people who only understand one 
 of them, or who don't understand either, can still follow the documentation.
 
 Regards,   Martin.
 
 
 On 2014/01/22 11:54, e@zzak.io wrote:
 > Issue #9438 has been reported by Zachary Scott.
 >
 > ----------------------------------------
 > misc #9438: Implementation naming
 > https://bugs.ruby-lang.org/issues/9438
 >
 > * Author: Zachary Scott
 > * Status: Open
 > * Priority: Normal
 > * Assignee: Zachary Scott
 > * Category: doc
 > * Target version: current: 2.2.0
 > ----------------------------------------
 > There seems to be an unclear decision on what to call this implementation.
 >
 > We should make a decision between CRuby and MRI and update relating documentation to use one of them.
 >
 > This discussion is based off a [ticket on ruby-lang.org](https://github.com/ruby/www.ruby-lang.org/commit/9c315c3#commitcomment-5120340), but also affects ruby-trunk source code as MRI is mentioned periodically.
 >
 >
 >

----------------------------------------
misc #9438: Implementation naming
https://bugs.ruby-lang.org/issues/9438#change-44487

* Author: Zachary Scott
* Status: Open
* Priority: Normal
* Assignee: Zachary Scott
* Category: doc
* Target version: current: 2.2.0
----------------------------------------
There seems to be an unclear decision on what to call this implementation.

We should make a decision between CRuby and MRI and update relating documentation to use one of them.

This discussion is based off a [ticket on ruby-lang.org](https://github.com/ruby/www.ruby-lang.org/commit/9c315c3#commitcomment-5120340), but also affects ruby-trunk source code as MRI is mentioned periodically.



-- 
http://bugs.ruby-lang.org/

In This Thread

Prev Next