Re: [sage-release] Re: Sage 7.0.rc1 released

2016-01-15 Thread Henri Girard
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

[sage-release] Re: Sage 7.0.rc1 released

2016-01-15 Thread Eric Gourgoulhon
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

Re: [sage-release] Re: Sage 7.0.rc1 released

2016-01-15 Thread Johan S . R . Nielsen
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

[sage-release] Re: Sage 7.0.rc1 released

2016-01-14 Thread kcrisman
> > > 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