65
65
and only contains the revisions in the current branch that are not already
66
66
in the branch at ``reference-url``.
68
If the local branch was created as a stacked branch, then you can
69
use the ``--stacked`` option to ``push`` and the *stacked-on* location
70
will be implicit. For example::
72
bzr branch --stacked source-url my-dir
75
bzr commit -m "fix bug"
69
.. The following text is hidden because bug 375013 breaks the example.
70
When bug 375013 is fixed, we should unhide this text.
71
- Andrew Bennetts, 10 March 2010
73
.. If the local branch was created as a stacked branch, then you can
74
.. use the ``--stacked`` option to ``push`` and the *stacked-on* location
75
.. will be implicit. For example::
77
.. bzr branch --stacked source-url my-dir
80
.. bzr commit -m "fix bug"
79
84
Limitations of stacked branches
80
85
-------------------------------
87
Currently, you cannot commit to a stacked branch, due to `bug 375013`_.
89
.. _bug 375013: https://bugs.launchpad.net/bzr/+bug/375013
82
91
The important thing to remember about a stacked branch is that the
83
92
stacked-on branch needs to be available for almost all operations. This is
84
93
not an issue when both branches are local or both branches are on the
96
Similarly, because most of the history is stored in the stacked-on repository,
97
operations like ``bzr log`` can be slower when the stacked-on repository is
98
accessed via a network.
88
101
Changing branch stacking
89
102
------------------------