Jim has commit access and does provide patches to improve the framework. This thread is about the ironruby tags though, and it would not help anyone other than IronRuby.
From: ironruby-core-boun...@rubyforge.org [mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Michael Letterle Sent: Wednesday, January 07, 2009 11:02 AM To: ironruby-core@rubyforge.org Subject: Re: [Ironruby-core] Comments in the RubySpec tag files If you're adding value to the RubySpec tests, the rubyspec guys are pretty good about giving commit access... spread the wealth! On Wed, Jan 7, 2009 at 2:40 AM, Shri Borde <shri.bo...@microsoft.com<mailto:shri.bo...@microsoft.com>> wrote: I added a few comments to critical_tags.txt like this: fails("need to track which thread owns critical lock"):Thread.critical defers exit This will help the next person who tries to fix the bug, and also as just documentation. However, I realized that Jim regenerates the tag files whenever he pulls down new RubySpec tests. So such comments will get lost. Jim, is that correct? If so, I will just not add such comments until we change the process so that the tags are not periodically regenerated from scratch. Shri _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org<mailto:Ironruby-core@rubyforge.org> http://rubyforge.org/mailman/listinfo/ironruby-core -- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
