On Apr 24, 11:51 pm, "Nicolas M. Thiery"
wrote:
> > > For information: the patch suggested on #5852 seems to work fine on my
> > > machine (macbook pro ubuntu intrepid)
>
> > Well, give the complexity of the patch why did you not do a formal
> > review then? :)
>
> I got scared by your comments
> > For information: the patch suggested on #5852 seems to work fine on my
> > machine (macbook pro ubuntu intrepid)
>
> Well, give the complexity of the patch why did you not do a formal
> review then? :)
I got scared by your comments that it could be system dependent, which
I don't want to dwe
On Apr 24, 6:27 pm, Gonzalo Tornaria wrote:
Hi Gonzalo,
> On Fri, Apr 24, 2009 at 10:06 PM, mabshoff wrote:
> > Gonzalo: Can you please post a proper patch for bugfixes you suggest -
> > I am happt to convert your diff into a proper patch attributed to you,
> > but if you did it would just be
On Fri, Apr 24, 2009 at 10:06 PM, mabshoff wrote:
> Gonzalo: Can you please post a proper patch for bugfixes you suggest -
> I am happt to convert your diff into a proper patch attributed to you,
> but if you did it would just be easier :)
It seems I have some trouble understanding what's a "pro
On Apr 24, 5:27 pm, "Nicolas M. Thiery"
wrote:
> On Fri, Apr 24, 2009 at 01:23:25AM -0700, mabshoff wrote:
Hi Nicolas,
> > I remember a discussion about the problem, but did not see any fixes
> > in 3.4.1. If someone knows a ticket and/or even better a patch please
> > let us know so we can g
On Fri, Apr 24, 2009 at 01:23:25AM -0700, mabshoff wrote:
>
>
>
> On Apr 24, 1:16 am, John Cremona wrote:
>
> Hi,
>
> > This problem has been around for a while. It works ok if you give an
> > absolute pathname.
> >
> > Having said that, I just realised that the testing I have been doing
>
On Apr 24, 1:16 am, John Cremona wrote:
Hi,
> This problem has been around for a while. It works ok if you give an
> absolute pathname.
>
> Having said that, I just realised that the testing I have been doing
> on a clone of 3.4.1 was working fine with a relative pathname.
>
> Perhaps it is
This problem has been around for a while. It works ok if you give an
absolute pathname.
Having said that, I just realised that the testing I have been doing
on a clone of 3.4.1 was working fine with a relative pathname.
Perhaps it is because Nicolas is working on an upgrade from 3.4.rc0
(as you
On Apr 24, 2009, at 12:21 AM, Nicolas M. Thiery wrote:
> Hi!
>
> I just upgrade to 3.4.1, and on my machine sage -t is broken for files
> in subdirectories. For example:
>
> --
>
> zephyr-~sage-main/sage>sage -t m
