On 9/5/07, perryn <[EMAIL PROTECTED]> wrote: > > > #8052 > > This is a small patch I submitted about 5 months ago, but nothing > seems to have happened with it since. I'm not sure if this is because > it has simply been deemed low priority or if it just hasn't been > noticed by anyone. Is there something else I should have done to draw > attention to it?
I've updated your patch for latest trunk. Diff is now in smaller chunks, which is way better for readability. However, some unit tests still fail. After you fix this, get 3 community members to review the patch (2 except me) and then it will get the "verified" keyword. #8163 > > This is a scriptaculous problem that has caused us problems on my > current project, forcing us to fork scriptaculous. You should discuss script.aculo.us problems on Rails-spinoffs mailing list or the #prototype channel on freenode. I can see that a > number of patches have been submitted, so I am interested in wether it > is intended for this to be fixed in a upcoming release or not. Is > there a way to tell? No, not really. If you really solved the problem for yourself in the company, your best bet is to actually make a patch and submit it with the current ticket. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
