On 2010-12-04 23:34, Marco Streng wrote:
> In this particular case it were pari bugs 1143 (fixed in 12769) and
> 1144 (fixed an hour earlier it seems).
It's in my TODO list: #10430.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an ema
In this particular case it were pari bugs 1143 (fixed in 12769) and
1144 (fixed an hour earlier it seems).
On 3 dec, 18:50, Jeroen Demeyer wrote:
> On 2010-12-03 16:15, Marco Streng wrote:> I encountered a bug in pari 2.4.3
> (alpha) while working on a sage
> > ticket. I reported it to pari, and
> > On Fri, Dec 3, 2010 at 11:38 AM, Robert Bradshaw
> > > Apply foo.pyx, foo2.pyx
>
> > I mean of course foo.patch, foo2.patch :).
>
> > > This will "reset" the patch list at that point, any added patches will
> > > get (semi-intellegently) appended to the list.
>
> > > This will help reviewer
On 3 dic, 20:49, Robert Bradshaw wrote:
> On Fri, Dec 3, 2010 at 11:38 AM, Robert Bradshaw
> > Apply foo.pyx, foo2.pyx
>
> I mean of course foo.patch, foo2.patch :).
>
> > This will "reset" the patch list at that point, any added patches will
> > get (semi-intellegently) appended to the list.