redirected and shared working trees

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Yates wrote:
>>We are starting to have a few too many terms because of the
>>combinatorial problem. (w/ w/o working tree, shared repository, etc).
>>So it might be nice to break things down into their individual
>>components, and describe branches by what pieces they have.
> 
> 
> Please do this.  Such descriptions belong in both the wiki and
> the tutorial.

Hmm.  We could do

        branch (in repository) = repository branch (branch for short)
           branch + repository = standalone branch
checkout (pointing to repository) = ?repository checkout? ?shallow
checkout? (checkout for short)
checkout + branch + repository = standalone checkout

This would have repurcussions for the UI.

I think that checkouts would be most similar to bound branches in terms
of workflow, so "bzr checkout --standalone ..." could create a bound
branch.  "bzr checkout --standalone --new-branch ..." might create an
unbound branch.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDzo700F+nu1YWqI0RArWwAJoCb4ha5Q5tZrR+ZbHF5uSZ+qfOmACcDfxN
r+DOziO9ofJazC2K72HUYYE=
=deq+
-----END PGP SIGNATURE-----