← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/en/user-guide/stacked.txt

  • Committer: Mark Hammond
  • Date: 2009-01-12 01:55:34 UTC
  • mto: (3995.8.2 prepare-1.12)
  • mto: This revision was merged to the branch mainline in revision 4007.
  • Revision ID: mhammond@skippinet.com.au-20090112015534-yfxg50p7mpds9j4v
Include all .html files from the tortoise doc directory.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/stacked.txt
18
18
  than leaving them in a shared repository).
19
19
 
20
20
* Security is improved over shared repositories, because the stacked-on
21
 
  repository can be physically readonly to developers committing to stacked
 
21
  repository can be physically readonly to developers committing to stacked 
22
22
  branches.
23
23
 
24
24
These benefits make stacked branches ideal for various scenarios
83
83
stacked-on branch needs to be available for almost all operations. This is
84
84
not an issue when both branches are local or both branches are on the
85
85
same server.
86
 
 
87
 
 
88
 
Changing branch stacking
89
 
------------------------
90
 
 
91
 
Stacking of existing branches can be changed using the ``bzr reconfigure``
92
 
command to either stack on an existing branch, or to turn off stacking.
93
 
Be aware that when ``bzr reconfigure --unstacked`` is used, bzr will
94
 
copy all the referenced data from the stacked-on repository into the
95
 
previously stacked repository.  For large repositories this may take
96
 
considerable time and may substantially increase the size of the
97
 
repository.