How to change the branch a lightweight checkout points at?

[Mary Gardiner]

The quote is from bug 348208: https://bugs.launchpad.net/bugs/348208

Moving to the mailing list since this is now a workflow question (although the
bug is valid too, afaik).

On Tue, Mar 24, 2009, Robert Collins wrote:
> well bind always operates on branches, so yes, 'bzr bind' on a
> lightweight checkout will operate on the branch it points at. bzr bind
> in a lightweight checkout does have uses, but its not common.

As folks may recall, I started a thread a few months back about what a pain it
is to work in heavyweight checkouts without network access. I've since adapted
my workflow, so that it looks something like this:

1. I have a mainline at bzr+ssh://remote/remote-branch

2. On each machine I have a checkout of mainline at
   /local/local-heavyweight-checkout

3. In order to actually work, I create branches of
   /local/local-heavyweight-checkout at /local/feature-branch-1 ,
   /local/feature-branch-2 etc

4. I work in /local/working-tree, which is a lightweight checkout of
   /local/local-heavyweight-checkout (initially), and I use "bzr switch" to move
   it between feature branches, and commit into them on and offline

4. Periodically, when online, I move /local/working-tree back to being a
   lightweight checkout of /local/local-heavyweight-checkout , merge completed
   feature branches back in, and commit.

Anyway, my use-case for bzr bind was "damn, /local/working-tree is a
lightweight checkout of bzr+ssh://remote/remote-branch rather than
/local/local-heavyweight-checkout, I want to change that." Is this one of the
uses of bzr bind on lightweight checkouts Robert refers to? If not, how do I
accomplish this?

-Mary