Oh, one more prerequisite: we need to populate the commit field on trac (preferably automatically) so the patchbot can tell when a commit gets out of date. Alternatively, perhaps there's a way to query the commit a branch points to via http without having to fetch it?
- Robert On Thu, Aug 29, 2013 at 3:34 PM, Robert Bradshaw <rober...@gmail.com> wrote: > No. It's mostly done; I set out to finish it up just a couple of days ago > (but ran into a bunch of other issues trying to figure out what branch to > build, merge into, and the fact that tests didn't even all pass in the git > branch). Actually being able to pull, build, and pass tests is a > prerequisite; there are tickets out for this (#15120 and #14968) that need > to be merged. > > > On Thu, Aug 29, 2013 at 4:41 AM, Frédéric Chapoton > <fchapot...@gmail.com>wrote: > >> Hello, >> >> so far, the patchbot is not able to test the tickets given by a git >> branch (and it seems that it does not recognize the branch field) >> >> Would it be hard to get that working ? There are already several tickets >> with a git branch waiting for review (just one example #15054) >> >> Frederic >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-devel@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
