evolve: lock the working copy early in next and prev (issue5244)
Both next and prev depend on a consistent working copy, but were waiting to
take the lock until they were ready to alter the working copy.
Take the lock before reading the working copy state, and do not release it
until we're definitely not going to change the working copy.
recursive-include docs/figures *.svg
include docs/figures/hgview-example.png
include docs/*.rst
include docs/*.py
include docs/tutorials/*.t
include docs/makefile
include docs/static/*.svg
include hgext/__init__.py
include hgext/evolve.py
include hgext/pushexperiment.py
include hgext/simple4server.py
include setup.py
include README
include COPYING
include tests/*.t
include tests/*.py
include tests/_exc-util.sh
include tests/dummyssh
exclude tests/test-oldconvert.t
exclude tests/test-qsync.t
exclude tests/test-drop.t