Purpose: | Update a mirror of this branch. |
||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Usage: | bzr push [LOCATION] |
||||||||||||||||||||||||||||||||||||||||||
Options: |
|
||||||||||||||||||||||||||||||||||||||||||
Description: | The target branch will not have its working tree populated because this is both expensive, and is not supported on remote file systems. Some smart servers or protocols may put the working tree in place in the future. This command only works on branches that have not diverged. Branches are considered diverged if the destination branch’s most recent commit is one that has not been merged (directly or indirectly) by the source branch. If branches have diverged, you can use ‘bzr push –overwrite’ to replace the other branch completely, discarding its unmerged changes. If you want to ensure you have the different changes in the other branch, do a merge (see bzr help merge) from the other branch, and commit that. After that you will be able to do a push without ‘–overwrite’. If there is no default push location set, the first push will set it (use –no-remember to avoid setting it). After that, you can omit the location to use the default. To change the default, use –remember. The value will only be saved if the remote location can be accessed. The –verbose option will display the revisions pushed using the log_format configuration option. You can use a different format by overriding it with -Olog_format=<other_format>. |
||||||||||||||||||||||||||||||||||||||||||
See also: |