[RFC] make checkouts as much like bound branches as possible

[Aaron Bentley]

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

Olaf Conradi wrote:
> Hmm, let me rephrase this:
> 
> A lightweight checkout with a bound branch has the benefit of
> unbinding and taking your laptop offline, as the lightweight checkouts
> were part of a local shared repository.

So this is:
A bound branch at ~/bound-branch
A lightweight checkout of ~/bound-branch at ~/checkout

I really don't see the point of this.  Why wouldn't you just use the
bound branch's working tree?

> A lightweight checkout from a remote shared repository can't do that.
> 
> A normal checkout (bound branch) can, but that isn't part of a shared
> repository.

Any branch can be part of a shared repository.  In Erik's ideal workflow
there's a repository at ~/, and all his bound branches are part of it.

> So I would prefer our current situation of allowing one to bind a
> lightweight checkout.

So you are against double-binding as it applies to bound branches, but
you are for double-binding as it applies to lightweight checkouts?

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

iD8DBQFEKVng0F+nu1YWqI0RAluCAJ9q440C46r65E/6fz3noeW0wa9pTwCeIiSK
Aoc3cNprznaqjTiqEXNMVcA=
=xWVM
-----END PGP SIGNATURE-----