[PATCH V2] generaldelta: initialize basecache properly

[Tim Delaney]

On 22 September 2013 06:00, Tim Delaney <timothy.c.delaney at gmail.com> wrote:

> Just to be clear - pulling from a remote generaldelta repo (e.g. over ssh)
> to a local generaldelta repo will currently have the same effect as pulling
> from a non-generaldelta repo to a generaldelta repo - you get parent deltas
> in the local repo, but not the benefit of reordering that you get with a
> local clone. Is that correct? If so, it's still a win for me in terms of
> manifest size.
>

Interesting. I've just been able to try this - cloned a remote generaldelta
repo (running under Mercurial 2.4) pulled over ssh via Mercurial 2.7. The
remote repo had a 600MB manifest. The clone has a 27MB manifest. Cloning
over SSH gained the benefit of reordering, just like a local clone.

So under what circumstances would you *not* get the benefit of reordering?

Tim Delaney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130922/e6b5586e/attachment.html>