On Thursday, June 7, 2018 at 2:36:35 PM UTC+2, Timo Kaufmann wrote:
>
> In some cases where upstream has vanished and sage effectiely maintains 
> the project through patches anyways, it may be a better idea to just fork 
> the project.
>

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.

-- 
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.

Reply via email to