> > > As mentioned before, there are no incremental updates from 6.x. You need > to compile from scratch, e.g. after cleaning with "make distclean" or "git > clean -f -d -x". If you are still working on tickets based on 6.x then you > might want to use a separate git tree for sage 7. > > > I looked through several of the threads in sage-release but couldn't (quickly) find anything more detailed than this. What happened that Sage 7 is not upgradeable?
I think that it would then make sense to have some message print out if someone tries sage -upgrade (if that's even still supported) lest they hose their Sage install, that's been a problem with such updates in the past as well. Also, can you give a little more guidance on how to still use "old" git branches - can we just merge in the newest Sage or will that cause problems as well? Thanks, - kcrisman -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
