Re: [sage-devel] Patch messup - how do I recover ?

2010-02-08 Thread David Kirkby
On 7 February 2010 20:10, Peter Jeremy wrote: > On 2010-Feb-04 23:56:27 +, "Dr. David Kirkby" > wrote: >>There is another maths library which can be linked, rather than using >>-lm. That at least got around this for the previous case of this. > > For that matter, if anyone is aware of a suit

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-07 Thread Peter Jeremy
On 2010-Feb-04 23:56:27 +, "Dr. David Kirkby" wrote: >There is another maths library which can be linked, rather than using >-lm. That at least got around this for the previous case of this. For that matter, if anyone is aware of a suitably licensed C99 libm, I'd also be interested. Since w

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Dr. David Kirkby
Robert Bradshaw wrote: Does this look right? http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch Yes. Looks like another thing coming from Solaris having a non-optimal literal value for e (exp(1), decimal floating point literals, etc.). I'd much rather fix

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Dr. David Kirkby
Minh Nguyen wrote: Hi David, On Fri, Feb 5, 2010 at 7:34 AM, Dr. David Kirkby wrote: Does this look right? http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch I think you know this already, but it doesn't hurt to explicitly say so here. The commit must be

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Robert Bradshaw
On Feb 4, 2010, at 1:02 PM, Minh Nguyen wrote: Hi David, On Fri, Feb 5, 2010 at 7:34 AM, Dr. David Kirkby wrote: Does this look right? http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch I think you know this already, but it doesn't hurt to explicitly sa

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Minh Nguyen
Hi David, On Fri, Feb 5, 2010 at 7:34 AM, Dr. David Kirkby wrote: > Does this look right? > > http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch I think you know this already, but it doesn't hurt to explicitly say so here. The commit must be on one line. That

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Robert Bradshaw
On Feb 4, 2010, at 12:34 PM, Dr. David Kirkby wrote: Robert Bradshaw wrote: On Feb 4, 2010, at 12:03 PM, Dr. David Kirkby wrote: I created a patch to fix a numerical noise issue. Expected: 0.85914091422952255 Got: 0.85914091422952277 http://trac.sagemath.org/sage_trac/ticket/8185 After

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Dr. David Kirkby
Robert Bradshaw wrote: On Feb 4, 2010, at 12:03 PM, Dr. David Kirkby wrote: I created a patch to fix a numerical noise issue. Expected: 0.85914091422952255 Got: 0.85914091422952277 http://trac.sagemath.org/sage_trac/ticket/8185 After doing this, I realised I'd put too many dots on the

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Robert Bradshaw
On Feb 4, 2010, at 12:03 PM, Dr. David Kirkby wrote: I created a patch to fix a numerical noise issue. Expected: 0.85914091422952255 Got: 0.85914091422952277 http://trac.sagemath.org/sage_trac/ticket/8185 After doing this, I realised I'd put too many dots on the end, so instead of the

Re: [sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread John Cremona
You can edit the patch with a text editor if it is as trivial as this. And when you upload it again, you can opt to replace the earlier patch with the same name. John On 4 February 2010 20:03, Dr. David Kirkby wrote: > I created a patch to fix a numerical noise issue. > > Expected: >    0.85914

[sage-devel] Patch messup - how do I recover ?

2010-02-04 Thread Dr. David Kirkby
I created a patch to fix a numerical noise issue. Expected: 0.85914091422952255 Got: 0.85914091422952277 http://trac.sagemath.org/sage_trac/ticket/8185 After doing this, I realised I'd put too many dots on the end, so instead of the two needed, I'd put three. 0.85914091422952... On