Shallow branches question
Paul Moore
p.f.moore at gmail.com
Tue Mar 11 21:15:23 GMT 2008
On 11/03/2008, John Yates <jyates at netezza.com> wrote:
> Martin Pool writes:
>
> > With the current code, we try to access all the repositories,
> > so I believe it will just fail if the network is not accessible.
>
>
> Such behavior seems mislabeled if it is exposed as a _shallow_
> branch capability. It sounds to me more like a _lazy_ branch
> capability. My expection, based solely on connotation of the
> term shallow, would be that once I request explicit construction
> of such a beast its future peregrinations would be limited to my
> prescribed horizon.
Absolutely. An option to go to the source for "the rest" would be
acceptable, but to my mind, there is nothing "shallow" about a branch
that still works with the full history all the time (and just doesn't
store it all locally).
Paul.
More information about the bazaar
mailing list