# HG changeset patch # User Pierre-Yves David # Date 1537875872 -7200 # Node ID 1421ff5c5c96455caa47bfc669cf877729888740 # Parent 9b71aa222f8e0f1f4ca09265d2bc0db1284dd75a pullbundle: point out the output flooding issue from core Right now, we don't have a reliable progress report when using pullbundle. diff -r 9b71aa222f8e -r 1421ff5c5c96 hgext3rd/pullbundle.py --- a/hgext3rd/pullbundle.py Tue Sep 25 13:29:49 2018 +0200 +++ b/hgext3rd/pullbundle.py Tue Sep 25 13:44:32 2018 +0200 @@ -55,11 +55,15 @@ works. Yet they are already useful and used in production. Performances are expected to greatly improved in the final implementation, -especially if some of it end up being compiled. +especially if some of it end up being compiled code. This first implementation lacks the ability to server the cached bundle from a CDN. We'll want this limitation to be lifted quickly. +The way mercurial core report progress is designed for the receival of a single +changegroup. So currently using pullbundle means flooding the user with output. +This will have to be fixed. + Why is does this live in the same repository as evolve ======================================================