On Thu, May 5, 2011 at 6:21 AM, Dave McLain <dmcl...@gmail.com> wrote: > I got frustrated with the number of patches that wouldn't merge with trunk, > so like any sane person would at 2 in the morning I started writing a script > that would screen scrape the Ready For Commit report, download the patches > for every ticket and automatically try to merge them with -p0, -p1 and the > -R for both of those. It's 6am now, so I'm going to bed before throwing the > source up on github, but I'll post the results below and open source the > script in the morning (or afternoon). > The next step would be to automatically set the "Patch Needs Improvement" > bit, but I figured I probably ought to get some more opinions than just a > straw poll on #django-dev.
I think this is a great idea -- I love the idea of a patchbot that'd give some basic info about the patch and automate this one repetitive process. I'd be +1 on hooking it directly into Trac: "Hi, this is your friendly neighborhood patchbot! It looks like this patch won't apply against the latest trunk. The error was..." Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
