[#30995] [Bug #3523] win32 exception c0000029 on exit using fibers — B Kelly <redmine@...>

Bug #3523: win32 exception c0000029 on exit using fibers

19 messages 2010/07/02

[#31100] [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...>

Hello,

26 messages 2010/07/07
[#31148] Re: [rubysoc] Queue C-extension patch to come — Roger Pack <rogerdpack2@...> 2010/07/09

> As this it my first patch to Ruby, I don't know where to begin with.

[#31320] Re: [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...> 2010/07/16

Sorry for leaving this thread for so long. I've tried to finish the

[#31322] Re: [rubysoc] Queue C-extension patch to come — Aaron Patterson <aaron@...> 2010/07/16

On Sat, Jul 17, 2010 at 06:55:35AM +0900, Ricardo Panaggio wrote:

[#31324] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

NB: I am Ricardo's mentor for this project.

[#31331] Re: [rubysoc] Queue C-extension patch to come — Benoit Daloze <eregontp@...> 2010/07/17

On 17 July 2010 06:00, Caleb Clausen <vikkous@gmail.com> wrote:

[#31332] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

On 7/17/10, Benoit Daloze <eregontp@gmail.com> wrote:

[#31138] Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...>

Hi!

14 messages 2010/07/08
[#31146] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 7:04), Nikolai Weibull wrote:

[#31149] Re: Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...> 2010/07/09

On Fri, Jul 9, 2010 at 06:20, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#31150] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 18:28), Nikolai Weibull wrote:

[#31217] [Bug #3562] regression in respond_to? — Aaron Patterson <redmine@...>

Bug #3562: regression in respond_to?

14 messages 2010/07/12

[#31269] [Bug #3566] memory leak when spawning+joining Threads in a loop — Eric Wong <redmine@...>

Bug #3566: memory leak when spawning+joining Threads in a loop

14 messages 2010/07/13

[#31399] [Backport #3595] Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string — Dreamcat Four <redmine@...>

Backport #3595: Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string

17 messages 2010/07/21

[#31459] [Bug #3607] [trunk/r28731] Gem.path has disappeared? — Ollivier Robert <redmine@...>

Bug #3607: [trunk/r28731] Gem.path has disappeared?

22 messages 2010/07/23

[#31519] [Bug #3622] Net::HTTP does not wait to send request body with Expect: 100-continue — Eric Hodel <redmine@...>

Bug #3622: Net::HTTP does not wait to send request body with Expect: 100-continue

9 messages 2010/07/28

[ruby-core:31092] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9

From: James Tucker <jftucker@...>
Date: 2010-07-06 16:48:28 UTC
List: ruby-core #31092
On 6 Jul 2010, at 17:18, Evan Phoenix wrote:

> 
> On Jul 6, 2010, at 9:10 AM, James Tucker wrote:
> 
>> 
>> On 6 Jul 2010, at 16:49, Yusuke Endoh wrote:
>> 
>>> Issue #3140 has been updated by Yusuke Endoh.
>>> 
>>> 
>>> Hi,
>>> 
>>> I set a deadline of this discussion: 7/10 (Sat) 23:59 JST.
>>> 1.9.2 will be released in status quo unless we can agree on concrete
>>> solution and write a patch.
>>> 
>>> IMO, it is no use just to complain.  It is too late to broaden the
>>> discussion.  Let's focus on the issue at hand, and please write a
>>> patch yourself.
>> 
>> I have. http://github.com/rubygems/rubygems/compare/master...perflude
>> 
>>> Or, complain directly to the maintainer for rubygems.
>> 
>> I am.
>> 
>> Is the above patch to rubygems actually acceptable for inclusion (via rubygems/fast.rb) to be included into ruby as a replacement for gem_prelude?
> 
> No, the patch isn't acceptable as going into 1.9.2, because it has not gone through the normal rigor of rubygems testing. I see a few issues with it straight away.

After discussion various of the social and release engineering issues with Evan, I want to provide a +1 for his patch for the 1.9.2 release.

There are still remaining bugs with gem_prelude.rb that concern me, but in the interest of progress I agree we should move forward and address these in a more organised discussion between the rubygems team and the ruby team by the next release in order to reduce user error reports for all involved, and our users.

In This Thread