On Tue, 13 May 2014 18:30:26 William Stein wrote: > On Tue, May 13, 2014 at 6:23 PM, François Bissey > > <francois.bis...@canterbury.ac.nz> wrote: > > Hi all, > > > > If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage, > > they can review http://trac.sagemath.org/ticket/16299 > > I glanced at it for a second and noticed that [1] completely deletes > the entire SPKG.txt change history of that package. > > [1] > http://git.sagemath.org/sage.git/commit/?h=62c44eee3c74b71ce7a08357d68c8fcb > 707ed0ae > > Is that intentional? For example, these lines get deleted forever: >
Yes. > I've never been a huge fan of SPKG.txt being our change log, rather > than just the revision history. However, the fact is that SPKG.txt is > an important part of documenting the change history, and it *does* get used > in debugging [2], so I'm not sure we can just delete it. > > [2] http://trac.sagemath.org/ticket/15178 > I am aware of this. Although historically I chased those through hg commits were possible in the past. I know that the squashing of the changelog in the new style sage is unpopular in some quarters but I am sticking to the official line. Someone wanting to dig the pre-git era, not always well maintained, changelog in SPKG.txt is welcome to do it from a copy of sage 5.12. Francois -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
