Mercurial > evolve
changeset 4141:1421ff5c5c96
pullbundle: point out the output flooding issue from core
Right now, we don't have a reliable progress report when using pullbundle.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Tue, 25 Sep 2018 13:44:32 +0200 |
| parents | 9b71aa222f8e |
| children | 683ceec8d37e |
| files | hgext3rd/pullbundle.py |
| diffstat | 1 files changed, 5 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- 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 ======================================================