Pushing to Bzr branches

When you have worked on your changes and want to push them to a remote branch, do the following in the local branch:

To rename or move files, run bzr mv OLD NEW. This helps to keep the resulting diff meaningful, and also works after the fact.
If you have added files, run bzr add . in the branch root. This starts tracking any files in the branch that are currently unknown.
If you have removed files, run bzr remove. In most cases, this should automatically stop tracking files that are no longer in the branch.
To check the status of the branch, run bzr status.
Commit your changes by running bzr commit. This will open a text editor to enter the commit message.
After you have done one or more commits, run bzr push LOCATION to push your changes to a remote branch.

The commit message should summarize all the changes you have done after the last commit. You can specify it directly by using -m MESSAGE, and link a bug report to the commit by using --fixes lp:BUGNO.


	When you are working on a branch and are making several changes that aren't related to each other, it is recommended that you do several commits. This helps to keep the commit log clean and makes it easier to find any issues that certain changes may have introduced.


	When you push to a remote branch the first time, you will need to specify the branch location. In most cases, it will follow the format `lp:~username/projectname/branchname`. This pushes your code to a personal remote branch. On subsequent pushes, you can omit the branch location, as Bzr will have saved your previous push location in the local branch configuration.


Getting and updating Bzr branches		Submitting merge proposals