comparison mercurial/helptext/config.txt @ 49200:71774d799de7

auto-upgrade: skip the operation if the repository cannot be locked This seems like a fine default behavior for now. If some users wants something more aggressive we can make the behavior configurable in the future. Differential Revision: https://phab.mercurial-scm.org/D12619
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Tue, 05 Apr 2022 05:01:58 +0200
parents 411d591e0a27
children 9e203cda3238
comparison
equal deleted inserted replaced
49199:575f3dedb69a 49200:71774d799de7
955 Automatic upgrade means that any process accessing the repository will 955 Automatic upgrade means that any process accessing the repository will
956 upgrade the repository format to use `dirstate-v2`. This only triggers if a 956 upgrade the repository format to use `dirstate-v2`. This only triggers if a
957 change is needed. This also applies to operations that would have been 957 change is needed. This also applies to operations that would have been
958 read-only (like hg status). 958 read-only (like hg status).
959 959
960 If the repository cannot be locked, the automatic-upgrade operation will be
961 skipped. The next operation will attempt it again.
962
960 This configuration will apply for moves in any direction, either adding the 963 This configuration will apply for moves in any direction, either adding the
961 `dirstate-v2` format if `format.use-dirstate-v2=yes` or removing the 964 `dirstate-v2` format if `format.use-dirstate-v2=yes` or removing the
962 `dirstate-v2` requirement if `format.use-dirstate-v2=no`. So we recommend 965 `dirstate-v2` requirement if `format.use-dirstate-v2=no`. So we recommend
963 setting both this value and `format.use-dirstate-v2` at the same time. 966 setting both this value and `format.use-dirstate-v2` at the same time.
964 967
1006 Automatic upgrade means that any process accessing the repository will 1009 Automatic upgrade means that any process accessing the repository will
1007 upgrade the repository format to use `dirstate-tracked-hint`. This only 1010 upgrade the repository format to use `dirstate-tracked-hint`. This only
1008 triggers if a change is needed. This also applies to operations that would 1011 triggers if a change is needed. This also applies to operations that would
1009 have been read-only (like hg status). 1012 have been read-only (like hg status).
1010 1013
1014 If the repository cannot be locked, the automatic-upgrade operation will be
1015 skipped. The next operation will attempt it again.
1016
1011 This configuration will apply for moves in any direction, either adding the 1017 This configuration will apply for moves in any direction, either adding the
1012 `dirstate-tracked-hint` format if `format.use-dirstate-tracked-hint=yes` or 1018 `dirstate-tracked-hint` format if `format.use-dirstate-tracked-hint=yes` or
1013 removing the `dirstate-tracked-hint` requirement if 1019 removing the `dirstate-tracked-hint` requirement if
1014 `format.use-dirstate-tracked-hint=no`. So we recommend setting both this 1020 `format.use-dirstate-tracked-hint=no`. So we recommend setting both this
1015 value and `format.use-dirstate-tracked-hint` at the same time. 1021 value and `format.use-dirstate-tracked-hint` at the same time.
1081 1087
1082 Automatic upgrade means that any process accessing the repository will 1088 Automatic upgrade means that any process accessing the repository will
1083 upgrade the repository format to use `share-safe`. This only triggers if a 1089 upgrade the repository format to use `share-safe`. This only triggers if a
1084 change is needed. This also applies to operation that would have been 1090 change is needed. This also applies to operation that would have been
1085 read-only (like hg status). 1091 read-only (like hg status).
1092
1093 If the repository cannot be locked, the automatic-upgrade operation will be
1094 skipped. The next operation will attempt it again.
1086 1095
1087 This configuration will apply for moves in any direction, either adding the 1096 This configuration will apply for moves in any direction, either adding the
1088 `share-safe` format if `format.use-share-safe=yes` or removing the 1097 `share-safe` format if `format.use-share-safe=yes` or removing the
1089 `share-safe` requirement if `format.use-share-safe=no`. So we recommend 1098 `share-safe` requirement if `format.use-share-safe=no`. So we recommend
1090 setting both this value and `format.use-share-safe` at the same time. 1099 setting both this value and `format.use-share-safe` at the same time.