Shallow branches question

[Erik Bågfors]

On Tue, Mar 11, 2008 at 4:40 PM, Nicholas Allen <allen at ableton.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>
>
> John Yates 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.
>  That's what I was hoping for too - and the ability to have some of the
>  remote revisions cached locally whenever they are retrieved (on an as
>  needed basis). So once they are read by a log command they are cached so
>  next time I ask for the log there is no need for network at all. It
>  seems like the current one will cache nothing locally except for locally
>  committed revisions. Still a great step from what Bazaar currently does
>  but the full thing would be so much better....
>

So basically, you are asking for shallow branches to save space, only
to have it grow in place until the branch become a full branch,
without notifying you?

I certainly hope that's not what you are saying here?

Regards,
Erik