Launchpad: Difference between revisions
(New page: == Here is a basic workflow I used to get started == bzr branch lp:openracing trunk (put the default openracing branch which is our trunk into a directory called trunk) cd trunk bzr push ...) |
|||
Line 2: | Line 2: | ||
bzr branch lp:openracing trunk (put the default openracing branch which is our trunk into a directory called trunk) | bzr branch lp:openracing trunk (put the default openracing branch which is our trunk into a directory called trunk) | ||
cd trunk | cd trunk | ||
bzr push bzr+ssh://keithcu@bazaar.launchpad.net/~keithcu/openracing/work | |||
(This creates a remote branch on the server called work for you to work with) | bzr push bzr+ssh://keithcu@bazaar.launchpad.net/~keithcu/openracing/work (This creates a remote branch on the server called work for you to work with) | ||
cd .. | cd .. | ||
Now you have to get it: | Now you have to get it: | ||
bzr branch lp:~keithcu/openracing/work | bzr branch lp:~keithcu/openracing/work | ||
cd work | cd work | ||
Party like crazy | Party like crazy | ||
bzr add (It will add your .hg directory if you aren't careful! bzr revert throws them away) | bzr add (It will add your .hg directory if you aren't careful! bzr revert throws them away) | ||
bzr commit -m "Party like it's 1929" | bzr commit -m "Party like it's 1929" | ||
bzr push lp:~keithcu/openracing/work (to push your changes to the remote server -- not strictly necessary, but it lets others pull from them, and backs your changes up in case your computer dies.) | bzr push lp:~keithcu/openracing/work (to push your changes to the remote server -- not strictly necessary, but it lets others pull from them, and backs your changes up in case your computer dies.) | ||
cd ../trunk | cd ../trunk | ||
bzr merge ../work | bzr merge ../work | ||
bzr commit -m "Applying work to trunk" | bzr commit -m "Applying work to trunk" | ||
Push changes to trunk so they are now in mainline | Push changes to trunk so they are now in mainline | ||
bzr push lp:openracing | bzr push lp:openracing | ||
To get your work branch up to date | To get your work branch up to date you can: | ||
you can: | |||
cd work | cd work | ||
bzr merge lp:openracing | bzr merge lp:openracing | ||
Revision as of 20:45, 17 February 2009
Here is a basic workflow I used to get started
bzr branch lp:openracing trunk (put the default openracing branch which is our trunk into a directory called trunk)
cd trunk
bzr push bzr+ssh://keithcu@bazaar.launchpad.net/~keithcu/openracing/work (This creates a remote branch on the server called work for you to work with)
cd ..
Now you have to get it:
bzr branch lp:~keithcu/openracing/work
cd work
Party like crazy
bzr add (It will add your .hg directory if you aren't careful! bzr revert throws them away)
bzr commit -m "Party like it's 1929"
bzr push lp:~keithcu/openracing/work (to push your changes to the remote server -- not strictly necessary, but it lets others pull from them, and backs your changes up in case your computer dies.)
cd ../trunk
bzr merge ../work
bzr commit -m "Applying work to trunk"
Push changes to trunk so they are now in mainline
bzr push lp:openracing
To get your work branch up to date you can:
cd work
bzr merge lp:openracing
Here are some notes but they aren't that helpful because they don't assume launchpad http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html
Longer doc: http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html