Need to move more intelligence into bundler
peter.arrenbrecht at gmail.com
Fri May 6 07:21:47 CDT 2011
On May 6, 2011 10:21 AM, "Sune Foldager" <cryo at cyanite.org> wrote:
> Benoit, I think we're gonna have to move even more intelligence into the
> Currently, group performs the main revision loop, and calls the bundler to
> each revision entry in the bundle.
> I think we'll need to move the loop into the bundler as well. In that way,
> bundler can have maximum flexibility to select deltaparents and to ask the
> what deltaparents IT uses, so it might strive to use the same, so the
deltas can be
> transfered directly. It can also test that it actually includes, in the
> revisions it would base against, which is important.
For shallow clones too, should we ever implement them in bundles.
> It would presumably no longer need to call revdiff, or at least not until
> already called deltaparent and perfomed some decisions.
> I am of course thinking of the scenario bundle2 + generaldelta/lwcopy
> What do you think?
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mercurial-devel