Your git is configured to spit out color escape sequenctes in scripts, that sounds generally like a bad idea. Whats the output of
$ git config color.ui You should set it to "auto" to show colors interactively but not in scripts. Having said that, we should probably work around borked git configurations by explicitly overriding it "git diff --color=never". Volunteers? On Tuesday, December 17, 2013 12:40:15 PM UTC, Nathann Cohen wrote: > > Hellooooo ! > > I also got the 3+2 errors on cmdline+maxima, but also 5 in sagedev.py and > 6 in patch.py. The errors are there : > > http://www.steinertriples.fr/a.log > > I also build it from github, not from the tarball O_o > > Nathann > > > On 17 December 2013 10:59, Jeroen Demeyer <[email protected]<javascript:> > > wrote: > >> On 2013-12-16 23:17, R. Andrew Ohana wrote: >> >>> I figured something would have been >>> done about the many tmp files that were being left around before stable >>> status. >>> >> Well, it's really just an annoyance. It's also not a regression (it must >> have existed in Sage 5.12 also), so I found it hard to justify as blocker >> issue. >> >> Jeroen. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-git" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > -- You received this message because you are subscribed to the Google Groups "sage-git" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
