On 17 December 2013 15:25, Nathann Cohen <[email protected]> wrote: > Hellloooooooooooo !! > > >> Note to the experts, in case you missed it the first time: There is a new >> branch "develop" on our git server, this will always point to the most >> recent beta/rc version. The master branch will always point to the most >> recent "release", except right now it will be identical to "develop" since >> there is no sage-on-git release yet. > > I just pulled from this develop branch and it worked fine. > Except that after running "sage -br" I still get a banner announcing Sage > 5.13. I then ran "make", and now it proudly says "Sage 6.0.rc1". >
Out of interest, how did you do all the above so quickly? I am workin on a 64-core machine which is being used by no-one else, and "make -j60" after "git pull origin master" is taking as long as an old-style build of Sage from a source tarball. > Hmmm.. Quick and clean. I'm going to love this git workflow ;-) Luck you, for me everything is slow and dirty still. John > > Nathann > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
