David Roe wrote:
+1 from me.
David
Thanks. How many +1's do we need before it gets done?
I can implement this easily and quickly, so don't mind doing it myself.
I currently have two versions of Sage I'd like to test, but can't do them in
parallel, despite the multiple processors I have.
Da
+1 from me.
David
On Fri, Feb 26, 2010 at 1:41 PM, David Kirkby wrote:
> If one runs 'make test' it creates a file test.log in $HOME/.sage/tmp
>
> If would be useful if that file had the date and time in its name, or
> even the PID so one could test multiple versions of Sage on the same
> machine
Nick Alexander wrote:
On 26-Feb-10, at 10:41 AM, David Kirkby wrote:
If one runs 'make test' it creates a file test.log in $HOME/.sage/tmp
If would be useful if that file had the date and time in its name, or
even the PID so one could test multiple versions of Sage on the same
machine at the
On 26-Feb-10, at 10:41 AM, David Kirkby wrote:
If one runs 'make test' it creates a file test.log in $HOME/.sage/tmp
If would be useful if that file had the date and time in its name, or
even the PID so one could test multiple versions of Sage on the same
machine at the same time.
+1. Could
If one runs 'make test' it creates a file test.log in $HOME/.sage/tmp
If would be useful if that file had the date and time in its name, or
even the PID so one could test multiple versions of Sage on the same
machine at the same time.
Dave
--
To post to this group, send an email to sage-devel@g
