On Sunday, November 16, 2014 8:50:41 PM UTC, john_perry_usm wrote: > > I get that (Travis mentioned it himself), but I'm not sure why it's > Travis' fault. First, the only change that needed to be made was a few > lines of Python code. If we could download & test patches as before, this > wouldn't be a problem. >
You can still do that, "git show <sha1>" is just a patch that you can apply by hand. Its going to be just as manual labor intensive and error prone as before, of course. Second, wouldn't that test against the development version have to be made > at some point, anyway? > The trac ticket shows whether there is a merge conflict, if there isn't one then there is no need to test it by hand. -- 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.
