[rfc] bzr-colo into core

[Alexander Belchenko]

John Arbash Meinel пишет:
>>> I've deleted the branch a lightweight checkout points to, and you just
>>> 'bzr switch --force' to another one. I don't know that we need to
>>> implement force to begin with. But realize you can always have a
>>> lightweight checkout pointing at a branch, and may not know it. (You can
>>> have a lightweight checkout of a branch on launchpad, for example.)
>> Well, as I understand colocated support in bzr-core there won't be a
>> lightweight checkout anymore, but new branch format with special
>> reference to active branch. Is it true? If that's true then deleting
>> active branch is not the same as deleting master branch of light
>> checkout, is it?
> 
> It really depends how we implement it. We *might* stick with the current
> bzr-colo model just to maintain compatibility with older clients. We've
> had a lot of push back in the past about format upgrades, so if we can
> do things without it, we should try.
> 
> In which case, we do just end up with a lightweight checkout pointing
> somewhere in a directory of branches.

In this case we should fix absolute path problem.

> Also note that the there are certainly arguments for being able to have
> multiple checkouts of your "bundle-of-branches". In which case, you
> still have the issue that someone might want to delete a branch which is
> referenced by some lightweight checkout. And I don't know that we want
> to refuse that. Though it could be nice to at least warn about it, to
> help prevent people shooting themselves in the foot.

That's understandable and in any case it will work as of today (manual 
`switch --force` required). But for the working tree of colo-thing 
itself the question is open.