You don't need the second statement unless you need a branch to add your own commits/modifications to Julia. You can at any point switch to the master branch with "git checkout master", but if you switch often, I'd recommend that you clone two copies so that you don't have to rebuild all the dependencies every time you switch. The makefiles might also contain bugs that might cause trouble when switching between branches that have diverged a lot.
Ivar kl. 16:29:22 UTC+1 mandag 27. oktober 2014 skrev David van Leeuwen følgende: > > Related to this: > > On Sunday, October 26, 2014 8:17:16 PM UTC+1, Stefan Karpinski wrote: >> >> If you do `git checkout release-0.3` then you will be on the >> `release-0.3` branch instead of `master`; you can then proceed exactly as >> you used to but will only get the relatively conservative changes on that >> stable release branch. >> >> > what exactly is the canonical way to compile a specific release from git? > (I still find it hard to understand the general concepts of git and/or how > one should work with branches and tags). I came up with > > $ git checkout v0.3.2 > $ git checkout -b version0.3.2 > > the latter statement just not to loose the possibility to continue with > master, later. But I can't imagine this is the recommended way. > > Cheers, > > ---david > > >> On Sun, Oct 26, 2014 at 3:11 PM, harven <har...@free.fr> wrote: >> >>> Hi, I am currently using julia v0.3.1-pre+4 under a debian gnu/linux >>> system and would like to upgrade to the latest stable version 0.3.2. Should >>> I recompile from source or is there a faster way? >>> >>> I used to do `git pull origin` but I guess that would retrieve the 0.4 >>> version of julia. >>> Thanks for your advice. >>> >> >>
