Checkout existing branch to established workspace (.moved)

[Eli Zaretskii]

> Date: Fri, 23 Mar 2012 16:52:29 -0400
> From: Aaron Bentley <aaron at aaronbentley.com>
> 
> So there are a lot of things that would be astonishing.  It would be
> astonishing if bzr co behaved differently from merge, pull, and other
> commands that interact with a working tree.

As a naive user, I'd actually start by asking what is the semantics,
both intended and actual, of "bzr co" or "bzr branch" into an already
existing workspace (= working tree, I presume).  To me, it seems they
are clearly meant to be used with empty working trees.  What am I
missing?