bzr should not allow push over shared repository

why is it dangerous? You are creating a branch at a given URL. There is nothing preventing you from doing it to any other place, such as:

bzr push .../repo/branch/subbranch

I personally think it could be very useful:
http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#nested-style-project-branch-sub-branch

But I may be one of the few people who feel that way.

Hmm, maybe it's my lack of understanding then. In my head I see a shared repository as being a place for branches to be stored underneath, not a branch itself, and that is certainly how we intend to use it.

I can however also see one of my colleagues accidentally pushing a branch over the shared repository itself, instead of underneath it, and I'm uncertain of what effect that would have on the shared repository itself. If the answer to that is zero, then I suppose it doesn't matter.

The nested branches example in the page given intrigues me. Is the history for all of those branches stored in the shared repository at the root? Does that happen in all cases (i.e. bzr always scans for the first shared repository it finds in its parent directories), or does it work by creating branches within branches which all refer to the same root shared repository?

bzr always scans for the first shared repository it can find in parent directories.

Hi,

Pushing a branch to the same location as a shared repository
does indeed cause no problems.

The only downside could be that the user doesn't realise that
the branch is also a shared repository and so deletes it.

We could detect the situation and provide an informative
message, but that's at the time that it happens, and
wouldn't necessarily help when the user came to delete
the branch.

I'm closing this report as "Won't fix", but if you disagree
then please feel free to re-open it.

Thanks,

James