##// END OF EJS Templates
clean: check that there are no conflicts after...
clean: check that there are no conflicts after As noted by Pulkit, there should never be any conflicts after doing a clean update, so `hg.clean()` should never return `True`. Let's check that assertion instead to clarify the code. The callers will now get a `None` instead of a `False` returned, but that should be fine (both result in a 0 exit status). Differential Revision: https://phab.mercurial-scm.org/D7984
Martin von Zweigbergk -
r44620:abcc82bf default
Show More
Name Size Modified Last Commit Author
/ contrib / packaging
debian
docker
hgpackaging
inno
macosx
wix
Makefile Loading ...
build-linux-wheels.sh Loading ...
builddeb Loading ...
buildrpm Loading ...
dockerdeb Loading ...
dockerrpm Loading ...
hg-docker Loading ...
linux-wheel-centos5-blacklist Loading ...
mercurial.spec Loading ...
packagelib.sh Loading ...
packaging.py Loading ...
requirements.txt Loading ...
requirements.txt.in Loading ...