creating checkouts, bound branches and standalone branches from an existing branch

[Wouter van Heyst]

On Mon, Feb 13, 2006 at 10:38:33AM +1100, Robert Collins wrote:
> On Sun, 2006-02-12 at 17:09 -0600, John A Meinel wrote:
> > Robert Collins wrote:
> > > On Sat, 2006-02-11 at 23:42 +0100, Denys Duchier wrote:
> > 
> > ...
> > 
> > > 
> > > It is unfortunate perhaps that it is extremely surprising to users of
> > > bk, hg, monotone, codeville and RCS. (suprisingly enough RCS with its
> > > 'vcs data is in the working tree' behaves essentially like a distributed
> > > system, just without good merging). 
> > > 
> > 
> > Since bzr is defined as a distributed rcs, I think we should keep that
> > behavior (create a local standalone (or local repo) branch is the
> > default result of 'get').
> 
> Hmmm. I think of bzr as a post-distributed RCS these days. We have
> support for both centralised and decentralised use cases, but our
> *primary* focus is delivering a lovable and effective RCS.
> 
> Also 'get' as a verb does not imply 'creation' to me. 'checkout' is a
> well known term for 'make a connected-to-the-server working area'. 'get'
> is AFAIK arch specific - baz and tla and larch and arx - and is just an
> alias to checkout. 

I know 'get' primarily from darcs.

Wouter van Heyst