Mercurial > public > mercurial-scm > hg
comparison mercurial/upgrade.py @ 46050:ad9dd4d333be
upgrade: drop an outdated comment
We can control the added/removed requirement through config for multiple years.
Differential Revision: https://phab.mercurial-scm.org/D9484
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Tue, 01 Dec 2020 15:50:12 +0100 |
| parents | f4f956342cf1 |
| children | 72b7b4bf3e65 |
comparison
equal
deleted
inserted
replaced
| 46049:a2a59cde9b9f | 46050:ad9dd4d333be |
|---|---|
| 72 revlogs.discard(upgrade) | 72 revlogs.discard(upgrade) |
| 73 | 73 |
| 74 # Ensure the repository can be upgraded. | 74 # Ensure the repository can be upgraded. |
| 75 upgrade_actions.check_source_requirements(repo) | 75 upgrade_actions.check_source_requirements(repo) |
| 76 | 76 |
| 77 # FUTURE there is potentially a need to control the wanted requirements via | |
| 78 # command arguments or via an extension hook point. | |
| 79 newreqs = localrepo.newreporequirements( | 77 newreqs = localrepo.newreporequirements( |
| 80 repo.ui, localrepo.defaultcreateopts(repo.ui) | 78 repo.ui, localrepo.defaultcreateopts(repo.ui) |
| 81 ) | 79 ) |
| 82 newreqs.update(upgrade_actions.preservedrequirements(repo)) | 80 newreqs.update(upgrade_actions.preservedrequirements(repo)) |
| 83 | 81 |