Mercurial > evolve

comparison README @ 5195:85640f1feced

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
readme: mention compat string format
author Anton Shestakov <av6@dwimlabs.net>
date Wed, 11 Mar 2020 16:11:04 +0700
parents f478ac0a818f
children d1f6cf85bfec
comparison
equal deleted inserted replaced
5194:f478ac0a818f 5195:85640f1feced
137 say in $HGSRC:: 137 say in $HGSRC::
138 138
139 $ cd tests 139 $ cd tests
140 $ python $HGSRC/tests/run-tests.py 140 $ python $HGSRC/tests/run-tests.py
141 141
142 When certain blocks of code need to cope with API changes in core Mercurial,
143 they should have comments in the ``hg <= x.y (commit hash)`` format. For
144 example, if a function needs another code path because of changes introduced in
145 02802fa87b74 that was first included in Mercurial 5.3, then the comment should
146 be::
147
148 # hg <= 5.2 (02802fa87b74)
149
150 See also tests/test-check-compat-strings.t.
151
142 Branch policy 152 Branch policy
143 ------------- 153 -------------
144 154
145 The evolve tests are highly impacted by changes in core. To deal with this, we 155 The evolve tests are highly impacted by changes in core. To deal with this, we
146 use named branches. 156 use named branches.