Yes, the "sage -upgrade" should just pull changes to the source repo and then rebuild. Will end up in precisely the same place as where you started it.
On Thursday, December 19, 2013 8:46:10 PM UTC, Justin C. Walker wrote: > > > On Dec 19, 2013, at 07:02 , Volker Braun wrote: > > > I'm pleased to announce the release of the first beta version. I've been > > working on merging the backlog of git tickets, though there is more to > come. > > > > If you are using git, note that the "master" branch is from now on > frozen > > to the sage-6.0 tree until 6.1 is finished. If you want to follow the > beta > > releases, you need to checkout the "develop" branch, for example with > the > > following commands: > > > > git fetch trac develop > > git checkout -b develop FETCH_HEAD > > > > Pulling the develop branch will always bring you to the most recent > beta/rc > > version. > > Is this the new version of "sage -upgrade", or does this do the moral > equivalent of the "git -clone" operation (leaving you with the "develop" > branch instead of the "master")? > > In particular, should you do this in the same directory where a previous > beta/rc lives? > > I'm still getting used to the git thingie. > > Thanks! > > Justin > > -- > Justin C. Walker, Curmudgeon at Large > Institute for the Absorption of Federal Funds > ----------- > My wife 'n kids 'n dogs are gone, > I can't get Jesus on the phone, > But Ol' Milwaukee's Best is my best friend. > ----------- > > > -- 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.
