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

[Aaron Bentley]

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

Olaf Conradi wrote:
> On 19/03/06, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:
>>I'd like to propose that checkouts have a special proxy branch, a
>>CheckoutBranch
...
> This would mean that a lightweight checkout can't be bound to another branch.
> 
> I thought there wouldn't be a sane use case for that, but thought of
> this later on...
> 
> Suppose a developer is working on a mainline using bound branches as
> described by LockStepDevelopment [1], but also wants to keep branches
> from other developers on his machine.
> 
> So he creates a shared repository on his machine and creates a tree of
> lightweight checkouts of mainline for his own stuff and experimental
> checkouts of other developers.
> 
> He binds his own checkout to the remote mainline and develops on that
> working tree for stable fixes and keeps the experimental branches in
> the same local shared repository.
> 
> With lightweight checkouts as bound branches he can't use this
> construct. If he wants to put everything in a local shared repository
> he can't bind to the remote one and has to push everything.

Perhaps the solution to that is to make bound branches support this.
It's certainly something their API can represent, and apparently people
like Erik want to use bound branches wherever I would use lightweight
checkouts.

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

iD8DBQFEKUIF0F+nu1YWqI0RAqMPAJ9w2Gr5yaSXJS7xOn+Aorjbv67TxgCfS9a7
jIp2CNhT6EyEE8PBWrzjaBM=
=iAHV
-----END PGP SIGNATURE-----