83
83
This usage fits the scenario described in the Motivation section.
85
If the local branch was created as a stacked branch, then you can
86
use the ``--stacked`` option to ``push`` and the *stacked-on* location
87
will be implicit. For example::
89
bzr branch --stacked source-url my-dir
92
bzr commit -m "fix bug"
86
.. The following text is hidden because bug 375013 breaks the example.
87
When bug 375013 is fixed, we should unhide this text.
88
- Andrew Bennetts, 10 March 2010
90
.. If the local branch was created as a stacked branch, then you can
91
.. use the ``--stacked`` option to ``push`` and the *stacked-on* location
92
.. will be implicit. For example::
94
.. bzr branch --stacked source-url my-dir
97
.. bzr commit -m "fix bug"
96
101
Limitations of stacked branches
97
102
-------------------------------
104
Currently, you cannot commit to a stacked branch, due to `bug 375013`_.
106
.. _bug 375013: https://bugs.launchpad.net/bzr/+bug/375013
99
108
The important thing to remember about a stacked branch is that the
100
109
stacked-on branch needs to be available for almost all operations. This is
101
110
not an issue when both branches are local or both branches are on the
113
Similarly, because most of the history is stored in the stacked-on repository,
114
operations like ``bzr log`` can be slower when the stacked-on repository is
115
accessed via a network.
105
118
Changing branch stacking
106
119
------------------------
added
removed
doc/en/user-guide/stacked.txt
