Re: [sage-release] Re: Sage 7.0.rc1 released
Thanks... Because each time I get a new develop version. Try it next version. Henri Le 15/01/2016 11:40, Johan S. R. Nielsen a écrit : If you already have a nice compiled version of latest develop, you can merge in your old branch *into* develop. With latest develop checked out, run the following: 1. git checkout -b "old_is_new" 2. git fetch 3. git merge trac/ 4. make Step 2 is only if you don't already have the latest version of that ticket. Compared to the newly compiled develop, this will touch only the files that were modified in your ticket. That saves a lot of compilation time when you're working on branches that have fallen far behind. That goes whether or not latest develop broke backwards compatibility. Best, Johan kcrisman writes: 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? If moving from a new branch to an old branch, you can either - merge in latest develop, or - make distclean && make Second option isn't very sustainable if you have to do it a lot, though. -- 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.
[sage-release] Re: Sage 7.0.rc1 released
built OK + make ptestlong passed on Ubuntu 15.10 x86_64 Xeon E5-2623 + 16 GB RAM. -- 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.
Re: [sage-release] Re: Sage 7.0.rc1 released
If you already have a nice compiled version of latest develop, you can merge in your old branch *into* develop. With latest develop checked out, run the following: 1. git checkout -b "old_is_new" 2. git fetch 3. git merge trac/ 4. make Step 2 is only if you don't already have the latest version of that ticket. Compared to the newly compiled develop, this will touch only the files that were modified in your ticket. That saves a lot of compilation time when you're working on branches that have fallen far behind. That goes whether or not latest develop broke backwards compatibility. Best, Johan kcrisman writes: >> 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? >> >> If moving from a new branch to an old branch, you can either >> - merge in latest develop, or >> - make distclean && make >> >> > Second option isn't very sustainable if you have to do it a lot, though. -- -- 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.
[sage-release] Re: Sage 7.0.rc1 released
> > > 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.
