Michael Hudson wrote:
> Public bug reported:
>
> Demo:
Is this because you are trying to use incremental pull to get around
other issues? (bzr pull -r 100; bzr pull -r 200; etc)?
Certainly AIUI, I believe Jelmer has issues with some sources not
providing lookup ability. For example 'bzr-git', the git protocol
doesn't let you inspect the info, just pull the whole thing and inspect
it locally. (you can't walk the graph to determine what '-r -10' is.)
I don't know if bzr-hg suffers from the same problem. I don't know the
hg protocol that well.
(To say that, bzr-git and bzr-hg may always have to do a full fetch,
they may not have to do a full conversion.)
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Hudson wrote:
> Public bug reported:
>
> Demo:
Is this because you are trying to use incremental pull to get around
other issues? (bzr pull -r 100; bzr pull -r 200; etc)?
Certainly AIUI, I believe Jelmer has issues with some sources not
providing lookup ability. For example 'bzr-git', the git protocol
doesn't let you inspect the info, just pull the whole thing and inspect
it locally. (you can't walk the graph to determine what '-r -10' is.)
I don't know if bzr-hg suffers from the same problem. I don't know the
hg protocol that well.
(To say that, bzr-git and bzr-hg may always have to do a full fetch,
they may not have to do a full conversion.)
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
o1p0ACgkQJdeBCY SNAAMtDwCg0934Q t5h1AfGXwi7kGpq XcSW DVN7rT+ vce0XxHiPcd
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAku
oJkAoK9dCssAg/
=ZEjX
-----END PGP SIGNATURE-----