comparison mercurial/requirements.py @ 46334:4b0192f592cf

share: move share safe functionality out of experimental The share-safe functionality is complete and all configuration options are implemented. The behavior is well discussed on mailing list and in reviews. Let's unmark this as experimental to solve a chichen and egg issue. Differential Revision: https://phab.mercurial-scm.org/D9823
author Pulkit Goyal <7895pulkit@gmail.com>
date Mon, 18 Jan 2021 19:16:49 +0530
parents d252f51ab032
children ee91966aec0f
comparison
equal deleted inserted replaced
46333:2eb5fe13461b 46334:4b0192f592cf
53 RELATIVE_SHARED_REQUIREMENT = b'relshared' 53 RELATIVE_SHARED_REQUIREMENT = b'relshared'
54 54
55 # A repository with share implemented safely. The repository has different 55 # A repository with share implemented safely. The repository has different
56 # store and working copy requirements i.e. both `.hg/requires` and 56 # store and working copy requirements i.e. both `.hg/requires` and
57 # `.hg/store/requires` are present. 57 # `.hg/store/requires` are present.
58 SHARESAFE_REQUIREMENT = b'exp-sharesafe' 58 SHARESAFE_REQUIREMENT = b'share-safe'
59 59
60 # List of requirements which are working directory specific 60 # List of requirements which are working directory specific
61 # These requirements cannot be shared between repositories if they 61 # These requirements cannot be shared between repositories if they
62 # share the same store 62 # share the same store
63 # * sparse is a working directory specific functionality and hence working 63 # * sparse is a working directory specific functionality and hence working