bazaar Digest, Vol 80, Issue 44

[Adrian Wilkins]

On 27/10/11 07:58, "Stephen J. Turnbull" <stephen at xemacs.org> wrote:
> I see.  So the only overhead here is the branch metadata (assuming
> you're in a shared repo).  And I take it that
>
>      bzr switch -r 42 -b newbranch
>
> creates a branch whose tip is r42 with the name "newbranch", switches
> the workspace to the new branch, and updates the current workspace to
> tip aka r42?

Alas, this does not work at present, see :

https://bugs.launchpad.net/bzr/+bug/733225

If you want branches of a non-tip revision, you have to use the normal 
branch command.

My typical working folder looks like this (.repo is a normal folder ; I 
used to use one repository for all project, but the size of the history 
in some of them was getting onerous for the other projects ; I have a 
lot of large trees pulled from SVN branches).

/.repo/repo-project1
                     /branch1
                     /branch2
       /repo-project2
                     /branch1
                     /branch2

/project1-lightweight-checkout
/project2-lightweight-checkout

And I check out with

bzr co --lightweight .repo/project/branch project

New branches with

bzr switch -b newbranch

Switches with

bzr switch oldbranch


So it's "manual" co-location.