[#25936] [Bug:1.9] [rubygems] $LOAD_PATH includes bin directory — Nobuyoshi Nakada <nobu@...>

Hi,

10 messages 2009/10/05

[#25943] Disabling tainting — Tony Arcieri <tony@...>

Would it make sense to have a flag passed to the interpreter on startup that

16 messages 2009/10/05

[#26028] [Bug #2189] Math.atanh(1) & Math.atanh(-1) should not raise an error — Marc-Andre Lafortune <redmine@...>

Bug #2189: Math.atanh(1) & Math.atanh(-1) should not raise an error

14 messages 2009/10/10

[#26222] [Bug #2250] IO::for_fd() objects' finalization dangerously closes underlying fds — Mike Pomraning <redmine@...>

Bug #2250: IO::for_fd() objects' finalization dangerously closes underlying fds

11 messages 2009/10/22

[#26244] [Bug #2258] Kernel#require inside rb_require() inside rb_protect() inside SysV context fails — Suraj Kurapati <redmine@...>

Bug #2258: Kernel#require inside rb_require() inside rb_protect() inside SysV context fails

24 messages 2009/10/22

[#26361] [Feature #2294] [PATCH] ruby_bind_stack() to embed Ruby in coroutine — Suraj Kurapati <redmine@...>

Feature #2294: [PATCH] ruby_bind_stack() to embed Ruby in coroutine

42 messages 2009/10/27

[#26371] [Bug #2295] segmentation faults — tomer doron <redmine@...>

Bug #2295: segmentation faults

16 messages 2009/10/27

[ruby-core:26127] Re: [ANN] Ruby Developer's Meeting 20091013

From: Roger Pack <rogerdpack@...>
Date: 2009-10-16 17:24:36 UTC
List: ruby-core #26127
> =3D=3D Regarding maintainers

> =E2=86=92 there is a tendency for proposals for new features to be ignore=
d
> because noone has the authority to reject them

Is this going to be remedied somehow, then?

> =E2=86=92 how about introducing the concept of committers with limited ri=
ghts?
> =E2=86=92 for the moment, add them as contributors to Redmine, and have t=
hem
> close/reject tickets, and see how it turns out (motion passed)
> =E2=86=92 the final to decision to accept them as committers will be made=
 by matz

I noticed on http://redmine.ruby-lang.org/wiki/ruby/CommitterHowto
That it says "Send patches, send patches and send patches. Someday the
core team will say "OK, commit it by yourself""

I will assume that is the case with any upcoming doc patches I have.
If someone wants me to commit them by myself then I will need commit
rights :)
-r

In This Thread