Checkout existing branch to established workspace (.moved)

[Wouter van Heyst]

On Sat, Mar 24, 2012 at 10:24:57 +0200, Eli Zaretskii wrote:
> > 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?

As far as I know, `git checkout` does both `bzr checkout` as well as
`bzr switch`.  It seemed to me that switch is more natural in Kevins
case, but then he mentioned doing a checkout in a tarball drop, which
might make sense to handle from checkout.

Wouter