Hi guys,
So it sounds like I should have posted about my patch here in the first place :) (Thanks for taking a look at it Mislav, I'll take a look at the tests as soon as I get a chance.) In regards to the scriptaculous problem, there have already been a number of submitted patches for the problem ( in fact we just copied one of them to make ours), so I didn't see the point in submitting another one. I was just interested in if there was a way to see when and if those patches were planned to be applied. The answer seems to be to simply ask on the mailing list ( in this case the scriptaculous list) I'll do that now :) thanks for your help Perryn On Sep 5, 8:55 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> wrote: > On 9/5/07, Gabe da Silveira <[EMAIL PROTECTED]> wrote: > > > > > Posting here with a code review request is always a good idea for > > important patches that seem to get lost in the shuffle. In addition, > > calling attention to the issue on IRC or in other mailing lists or on blogs > > will help get the right people involved. > > I also support bumping the patches one or two times on either the ML or IRC. > It doesn't even have to be months later, it can only be 2-3 weeks later > after the original patch didn't get attention. No comments on a ticket can > also mean that the ticket description is vague and that the patch may not be > self-descriptive (too complicated or not very well done). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
