repositories - pinning down discovery behaviour

[Denys Duchier]

Robert Collins <robertc at robertcollins.net> writes:

> So, I have reversed my position there - I'm seeking a +1 on:
> 'support nested branches using a single repository' and
> 'shared repositories will have a marker of some sort'

I suggested assigning a uuid at shared-repo creation time to make (what I
called) "inheritance" a bit more robust.

> This makes the search for a repository:
> for each .bzr dir containing self.bzrdir:
>   if there is a repository and its not marked as shared, stop
>   if there is no repository, continue

for shared repo discovery at branch creation time, the marker is simply the
existence of the uuid.

if a branch remembers its repo's uuid, shared repo recovery through inheritance
becomes:

for each .bzr dir containing self.bzrdir:
   if there is a repo and it has a uuid and this is the expected uuid, stop
   else continue

Cheers,

--Denys