435
435
Create a new checkout, associated with a new repository branch.
437
When you cbranch, bzr looks up the repository associated with your current
438
directory in locations.conf. It creates a new branch in that repository
439
with the same name and relative path as the checkout you request.
441
The locations.conf parameter is "cbranch_root". So if you want
442
cbranch operations in /home/jrandom/bigproject to produce branches in
443
/home/jrandom/bigproject/repository, you'd add this:
445
[/home/jrandom/bigproject]
446
cbranch_root = /home/jrandom/bigproject/repository
448
Note that if "/home/jrandom/bigproject/repository" isn't a repository,
449
standalone branches will be produced. Standalone branches will also
450
be produced if the source branch is in 0.7 format (or earlier).
437
When you cbranch, bzr looks up a target location in locations.conf, and
438
creates the branch there.
440
In your locations.conf, add the following lines:
441
[/working_directory_root]
442
cbranch_target = /branch_root
443
cbranch_target:policy = appendpath
445
This will mean that if you run "bzr cbranch foo/bar foo/baz" in the
446
working directory root, the branch will be created in
447
"/branch_root/foo/baz"
449
NOTE: cbranch also supports "cbranch_root", but that behaviour is
452
452
takes_options = [Option("lightweight",
453
453
help="Create a lightweight checkout"), 'revision']
added
removed
__init__.py
