See also http://doc.sagemath.org/html/en/developer/packaging.html#how-to-maintain-a-set-of-patches
On Friday, June 8, 2018 at 4:05:47 AM UTC-7, Dima Pasechnik wrote: > > > > On Friday, June 8, 2018 at 9:25:33 AM UTC+1, Jeroen Demeyer wrote: >> >> On 2018-06-08 07:47, Ralf Stephan wrote: >> > It might be an idea to semi-automatize this, i.e., build a tool that >> > takes a Sage version and creates forks of some packages A,B on github >> > under sage/sage-A, sage/sage-B. >> >> Which problem would that solve? >> >> patches are not the best way to update things. VCSs are much better... > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
