Shallow branches question

[Nicholas Allen]

-----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....

Nick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFH1qfSbpmWsXfOU58RAvZEAJ9jGIohQIE50UA3nx5x64C51lZMtwCglJHX
CJp9qy0zKaR8dAtTD7IUAZg=
=Ce0o
-----END PGP SIGNATURE-----