You can go from release to master, but you can't go back to release if you do. On 12 Jun 2015 17:38, <[email protected]> wrote:
> Ok. Thank you all. > Last question: I run 4.0.4. Is it possible to upgrade to master branch or > have i to stay in release branch? > > -------------------------------------------- > Matthias Sund <[email protected]> schrieb am Do, 11.6.2015: > > Betreff: Aw: AW: Re: Development branch > An: [email protected] > CC: [email protected] > Datum: Donnerstag, 11. Juni, 2015 22:51 Uhr > > > You may also use the source repo. You should be able to > check out tagged revision v4.0.5 before you start the > build: > > 'git checkout v4.0.5'. > > > > In case you want to follow a release branch, let us > say 4.0, you can check this revision out with: > > 'git checkout DragonFly_RELEASE_4_0' and update > your local copy as usual with > > 'git pull'. > > > > > The master branch really is the devoted to DragonFly > development and that is you get every developer commit > whereas the release branches only contain revisions of > DragonFly releases. > > > > > Gesendet: Donnerstag, 11. Juni 2015 um 17:40 > Uhr > > Von: nans_nans1 <[email protected]> > > An: "Matthias Sund" > <[email protected]>, [email protected] > > Betreff: Aw: AW: Re: Development branch > > > > > Ok. But sorry for my further question: And how can i > update to 4.0.5 if i running 4.0.4? > > What is here difference? > > > > > Von > Samsung Mobile gesendet > > > > > > > > -------- Ursprüngliche Nachricht -------- > > Von: Matthias Sund <[email protected]> > > Datum: 11.06.2015 14:37 (GMT+01:00) > > An: [email protected] > > Betreff: Aw: AW: Re: Development branch > > > > > > > > Hi, > > > > you need to check out the master branch from DragonFly > source repo: > > > > cd /usr; make src-create && make > src-checkout > > > > You should have checked out master branch after that. > You might check that with: > > > > cd /usr/src; git branch > > > > which should write "* master" to the > terminal. > > > > To actually upgrade the system, you need to issue the > following steps with optional steps in paranthesis: > > > > 1. cd /usr/src > > 2. (git pull) updates the sources to the latest devel > version > > 3. make buildworld && make buildkernel > > 4. make installkernel && make installworld > && make upgrade > > 5. reboot > > > > In step 3, you may use "make -j[number of > available CPU cores] ..." to speed up the build > processes. > > > > Regards > > Matthias > > > Gesendet: Donnerstag, 11. Juni 2015 um 13:49 > Uhr > > Von: nans_nans1 <[email protected]> > > An: "John Marino" > <[email protected]>, [email protected] > > Betreff: AW: Re: Development branch > > > Thank you. But, please, give me instructions what i > have to do in detail. > > > > > > > Von > Samsung Mobile gesendet > > > > > > > > -------- Ursprüngliche Nachricht -------- > > Von: John Marino <[email protected]> > > Datum: 11.06.2015 13:25 (GMT+01:00) > > An: [email protected],[email protected] > > Betreff: Re: Development branch > > > > > > On 6/11/2015 13:18, [email protected] wrote: > > > Hi > > > > > > is it possible to stay in development branch for every > update forever? > > > > > > If yes, how can i do this? > > > > > > > > > Build from source and have git set to the "master" > branch. By > > definition, it is always development. It got changed to > version 4.3 > > (from 4.1) this morning. > > > > > > > > > >
