Merge two checkouts in bazaar -
I'm just starting with the market, and I have found that the checkout feature is the way I work - Master copy ", I can do some development and then make changes to the new directory. It then updates the "master copy"
But what if I (for example) are working on two projects, changing the different parts of the code? Says:
~ / master - master copy bzr with master ./gui bzr co master. / Engine
So I'm doing GUI-related stuff ./gui in directory and under-the-hood stuff. How do I make my changes? If I do the first GUI then the engine, I think any collision in the engine will be flagged?
Is there a way to merge and engine the engine, and then only works to copy a master?
Maybe I'm working on the mouse, but also on the goai . If I want to merge code with GUI and mouse, and then I am committed to mastering, then what is the best way to manage it? Or in fact, if I also changed the GUI, keyboard and mouse, then:
bzr branch ./keyboard
I should merge into the hierarchy - i.e. the mouse + keyboard, then merge it with the geeks, then do the guru sign it?
I hope it is clear what I am trying to achieve! Thank you in advance for your time.
If you have two checkouts, you must first drag down any change in each step, Problems in each phase will likely be resolved. This is usually a good idea, because it is easy to solve conflicts over time and make sure that your code is not very different.
However, it seems that you want different developers working on "Gui" and "Engine", or you want to save your conflict solution for the development of both conflicts. In this case, you should probably make them as "independent branches" with "Bijar Branch". Each branch can use local commitment and can not worry about struggling with each other. Then when it comes time to merge, then you can do it in 3 ways, all of which are same Get the last result:
1. Mix one branch into another, then press it to master:
CD gui buzzer merge .. / engine # manually fix any conflict bzr commit bzr push #back up to The negative side for the above method is that there is an "engine" change in your "Guai" branch which is okay if you are going to throw both the branches. They are pushed back into the main line. But if you want to keep the branches for a long time, you can do the following: 2. Merge into main line: CD master buzzer merge ../gui bzr commit bzr merge ../engine # conflict conflict bzr commit
It is upside down that you still have "Gui" and "Engines" in the form of different branches, but before you are sure that they will work together, you have to do one with the guru. You might actually want:
create 3 merge bands:
bzr branch ~ / master gui-engine-merge cd gui-engine-merge bzr merge .. / Gui bzr commit bzr merge ../engine # Manually opposed conflict bzr Bzr push ~ / master # Since this branch was for merger only, you do not need it: cd .. rm -r gui-engine- Merge
Comments
Post a Comment