I was actually thinking of limiting the script to check only the recent patches (no use checking patches made years ago), and it doesn't have to be run on every commit. But then how recent and how frequently is it run? I don't really have any criteria for this. Full automation doesn't seem to be worth pursuing further. Thanks for all the info.
Though I wish I had access to Pratik's app :) On Oct 24, 1:41 pm, "Michael Koziarski" <[EMAIL PROTECTED]> wrote: > > Are you > > suggesting that some script goes through all patches on Trac after each > > commit to Rails trunk and checks if they still apply cleanly? That would be > > one heck of a post-commit hook. The idea is not bad, however. > > I know the SvK guys have talked about building something like this > into RT. But it just seems like you'd end up building a half-assed > DSCM tool... > > We already have the stale tickets report, the odds of the patches on > that list applying are pretty slim. > > http://dev.rubyonrails.org/report/69 > > If you feel like closing some old patches / reports, that's where to find > them. > > -- > Cheers > > Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
