Mercurial > public > mercurial-scm > hg
comparison mercurial/changegroup.py @ 32267:c2380b448265
caches: move the 'updating the branch cache' message in 'updatecaches'
We are about to remove the branchmap cache update in changegroup application.
There is a debug message alongside this update that we do not want to loose. We
move the message beforehand to simplify the test update in the next changeset.
The message move is quite noisy and isolating that noise is useful.
Most tests update are just line reordering since the message is issued at a
later point during the transaction.
After this changes, the message is displayed in more case since local commit
creation also issue it.
author | Pierre-Yves David <pierre-yves.david@ens-lyon.org> |
---|---|
date | Tue, 02 May 2017 22:27:44 +0200 |
parents | 4e6aab69a98b |
children | 24f55686a63d |
comparison
equal
deleted
inserted
replaced
32266:2b6692df1bdf | 32267:c2380b448265 |
---|---|
407 if srctype != 'strip': | 407 if srctype != 'strip': |
408 # During strip, branchcache is invalid but | 408 # During strip, branchcache is invalid but |
409 # coming call to `destroyed` will repair it. | 409 # coming call to `destroyed` will repair it. |
410 # In other case we can safely update cache on | 410 # In other case we can safely update cache on |
411 # disk. | 411 # disk. |
412 repo.ui.debug('updating the branch cache\n') | |
413 branchmap.updatecache(repo.filtered('served')) | 412 branchmap.updatecache(repo.filtered('served')) |
414 | 413 |
415 def runhooks(): | 414 def runhooks(): |
416 # These hooks run when the lock releases, not when the | 415 # These hooks run when the lock releases, not when the |
417 # transaction closes. So it's possible for the changelog | 416 # transaction closes. So it's possible for the changelog |