Mercurial > evolve
comparison hgext3rd/pullbundle.py @ 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 |
comparison
equal
deleted
inserted
replaced
| 4140:9b71aa222f8e | 4141:1421ff5c5c96 |
|---|---|
| 53 Both for stablerange and pullbundle use "simple" initial implementations. | 53 Both for stablerange and pullbundle use "simple" initial implementations. |
| 54 Theses implemenations focus on testing the algorithms and proving the features | 54 Theses implemenations focus on testing the algorithms and proving the features |
| 55 works. Yet they are already useful and used in production. | 55 works. Yet they are already useful and used in production. |
| 56 | 56 |
| 57 Performances are expected to greatly improved in the final implementation, | 57 Performances are expected to greatly improved in the final implementation, |
| 58 especially if some of it end up being compiled. | 58 especially if some of it end up being compiled code. |
| 59 | 59 |
| 60 This first implementation lacks the ability to server the cached bundle from a | 60 This first implementation lacks the ability to server the cached bundle from a |
| 61 CDN. We'll want this limitation to be lifted quickly. | 61 CDN. We'll want this limitation to be lifted quickly. |
| 62 | |
| 63 The way mercurial core report progress is designed for the receival of a single | |
| 64 changegroup. So currently using pullbundle means flooding the user with output. | |
| 65 This will have to be fixed. | |
| 62 | 66 |
| 63 Why is does this live in the same repository as evolve | 67 Why is does this live in the same repository as evolve |
| 64 ====================================================== | 68 ====================================================== |
| 65 | 69 |
| 66 There is no fundamental reasons for live in the same repository. However, the | 70 There is no fundamental reasons for live in the same repository. However, the |