repository/branch stacking - my current thoughts

Robert Collins robertc at
Tue Feb 5 22:54:45 GMT 2008

On Wed, 2008-02-06 at 09:32 +1100, Jonathan Lange wrote:
> On Feb 5, 2008 4:59 PM, Robert Collins <robertc at> wrote:
> ...
> >
> > A third way is to provide a location in the branch (or arguably a list,
> > but I think there is little reason to have an arbitrary list, and a
> > single pointer avoid things like 'which one to check first', and 'handle
> > some network issues as soft errors rather than hard errors').
> >
> I can't parse this. Provide a location for _what_ in the branch?

Of where external references can be resolved; the same style of location
as the other locations talked about earlier in the mail.

> [snip implications]
> > In terms of code layout, I think that delegation to other repositories
> > should be a core component of the Repository class; I don't think we
> > should attempt to do this via layering a decorator on the top, because
> > Repository is really a URL located resource in many places in our code
> > base, and a decorator doing magic has no URL of it's own.
> >
> >
> This sounds like it precludes the third option, but I'm not sure,
> since I don't understand the third option :)

I don't see why it would.

GPG key available at: <>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : 

More information about the bazaar mailing list