I would also add that tickets that don't get immediate attention will rarely get committed without some sort of followup action from the author. Often times the committers won't easily be able to evaluate the quality of a patch or the legitimacy of an issue, while the people who are affected by the issue may never see the patch to begin with. 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.
If someone thinks the patch is a bad idea they'll generally say so. Complete silence just means no one has had the time to evaluate the patch. -- Gabe da Silveira http://darwinweb.net --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
