Done: trac #9673 (http://trac.sagemath.org/sage_trac/ticket/9673). I asked for clear semantics of the "-tnew" flag, but from Simon's reply, this answers my question. Wouldn't it make sense, then, to have a flag for testing all changed files _as well as those depending on them_ (just as the -b flag works, I guess)?
By the way, I'm sorry if I have carried this thread somewhat off track. On Aug 3, 9:49 am, Minh Nguyen <nguyenmi...@gmail.com> wrote: > Hi Johan, > > On Tue, Aug 3, 2010 at 5:36 PM, Johan S. R. Nielsen > > <j.s.r.niel...@mat.dtu.dk> wrote: > > Why doesn't the Developer's Guide refer to > > "sage -tnew" for when doc-testing? > > Because no one has yet asked for such documentation, until now. Feel > free to open a documentation ticket on trac and filed that ticket > under component "documentation". > > -- > Regards > Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
