On Fri, Dec 3, 2010 at 12:12 PM, Jason Bandlow <jband...@gmail.com> wrote: > (cc'ing the sage-combinat folks who may not have seen this) > > Robert Bradshaw wrote: >> On this note: http://sage.math.washington.edu:21100/ticket/ > >>> It has some heuristics, but it's far from perfect. As people learn the >>> conventions of the buildbot, and the buildbot learns the conventions >>> of people, this will improve. Deleting old patches is not the right >>> solution, instead, write the following in any comment: >>> >>> Apply foo.pyx, foo2.pyx >> >> I mean of course foo.patch, foo2.patch :). >> >>> This will "reset" the patch list at that point, any added patches will >>> get (semi-intellegently) appended to the list. > > Huge +1 to this. Thank you very much for putting this together! And I > like your (initial?) solution to the problem of not having a trac field > for which patches to apply! > > By the way, is there a pointer to this anywhere other than this list > (where things get buried quickly)? Do you have source-code we can look > at? I realize it's all brand new...
I just added http://wiki.sagemath.org/buildbot , but don't have time to write much up right now. Feel free to add your collective wisdom, and I'll prune/edit/correct if need be. I don't think anything links to that, though the trac pages do link to the new site. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
