On 01/22/2014 07:16 PM, Johannes Lorenz wrote: >> No, it's wrong that you pull-rebase it. That's not something you ever >> have to do unless you're making changes to the code. >> >> Just clone the repository regularly with git clone: >> >> git clone git://github.com/LMMS/lmms.git >> cd lmms >> git checkout stable-0.4 >> >> Then build normally. After that, you can always update it to latest by >> going to the directory and doing a simple "git pull", no other arguments. > Isn't this wrong? I usually make forks, so the first time, I clone from my > fork. In the wiki is described how to make forks, and I think that one is > correct. > > Is it impossible to update my fork clone from the current code repository? > >
Well it depends: Do you plan on contributing code to LMMS? You only need to fork if you're going to contribute code or other changes to the software. If you just want the latest code, simply clone the original repository on your hard drive and compile it - that's it, no forks needed. If you however plan on contributing code to LMMS, then you need to fork. Then you clone your forked repository with git clone. Then you make the changes, commit them, and _then_ you use rebase on your fork. Then you push your changes to your own fork and create a pull request to get your contributions merged back to upstream. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
