On 3/30/2011 4:01 PM, Jelmer Vernooij wrote:
> This is fairly tricky to do efficiently with Mercurial; Mercurial itself
> just hides tags that point at revisions not in the tip ancestry.
>
> We only find out the tags at the point that the tip contents have been
> fetched, so we'd have to do completely new pulls for the revisions that
> are missing.
>
> ** Changed in: bzr-hg
> Milestone: 0.2 => None
>
It seems like you could just do an elongated fetch. So you first fetch
the current tip, then after you have it, you see what other data you
need, and send that along.
Certainly we already do that in bzr for fetching inventories chaining to
chk_bytes chaining to file texts.
I don't know the bzr-hg internals, but conceptually it doesn't seem like
we would have to know all the tags up front.
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
On 3/30/2011 4:01 PM, Jelmer Vernooij wrote:
> This is fairly tricky to do efficiently with Mercurial; Mercurial itself
> just hides tags that point at revisions not in the tip ancestry.
>
> We only find out the tags at the point that the tip contents have been
> fetched, so we'd have to do completely new pulls for the revisions that
> are missing.
>
> ** Changed in: bzr-hg
> Milestone: 0.2 => None
>
It seems like you could just do an elongated fetch. So you first fetch
the current tip, then after you have it, you see what other data you
need, and send that along.
Certainly we already do that in bzr for fetching inventories chaining to
chk_bytes chaining to file texts.
I don't know the bzr-hg internals, but conceptually it doesn't seem like
we would have to know all the tags up front.
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
TPT0ACgkQJdeBCY SNAANa9gCdHbs29 wakwdu/ TZWgFIplRVTp wpQfLFh/ KniYyW0s6
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAk2
fa8AoJypSNz7bae
=q+pY
-----END PGP SIGNATURE-----