Mercurial > evolve
changeset 5218:bf37ba1c80ee
evolve: fixed some typos in stablerangecache LONG_MESSAGE, fix #6279
| author | Yohann Rebattu <yohann@rebattu.fr> |
|---|---|
| date | Sat, 21 Mar 2020 15:04:18 +0100 |
| parents | 678a9223aad3 |
| children | 8431bb224862 |
| files | hgext3rd/evolve/stablerangecache.py |
| diffstat | 1 files changed, 3 insertions(+), 3 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext3rd/evolve/stablerangecache.py Fri Apr 03 19:10:29 2020 +0200 +++ b/hgext3rd/evolve/stablerangecache.py Sat Mar 21 15:04:18 2020 +0100 @@ -42,20 +42,20 @@ Your repository is probably big. -Stable range are used for discovery missing osbsolescence markers during +Stable ranges are used for discovery missing obsolescence markers during exchange. While the algorithm we use can scale well for large repositories, the naive python implementation that you are using is not very efficient, the storage backend for that cache neither. This computation will finish in a finite amount of time, even for repositories -with millions of revision and many merges. However It might take multiple tens +with millions of revision and many merges. However it might take multiple tens of minutes to complete in such case. In the future, better implementation of the algorithm in a more appropriate language than Python will make it much faster. This data should also get exchanged between server and clients removing recomputation needs. -In the mean time, got take a break while this cache is warming. +In the meantime, go take a break while this cache is warming. See `hg help -e evolve` for details about how to control obsmarkers discovery and the update of related cache.