Yes, I think it will be much more efficient to address these changes all at once. I would really prefer that, if possible.
I had seen the "reasons-to-invalidate-tickets" statement but was hoping this was a guideline, subject to context, and not a law. Thanks. On Thursday, June 11, 2015 at 8:31:29 AM UTC-7, kcrisman wrote: > > > >> http://doc.sagemath.org/html/en/developer/trac.html#reasons-to-invalidate-tickets >> > > I think what Nathann is trying to say is that it might be good to split > this up into smaller pieces. However, given the trouble you had getting > git to work, that might be something somewhat technically infeasible > without some help. > > That said, I've seen worse ;-) David, this looks like a great piece of > work - do you have some colleagues or students who might be able to help > review it without breaking it into smaller pieces? > -- 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/d/optout.
