discovery: ensure that missingheads are always heads of everything we tried This only alter the third block executed when: * repo have secret changeset * onlyheads is not None In other case findcommonoutgoing already had this behavior

phase: extracts heads computation logics from analyzeremotephases

phase: fix warning text from invalid remote phase add missing end of line and substitution.

mq-safety: don't apply safety on non-outgoing changeset When mq changeset are secret, they don't appear in outgoing and won't be pushed. So it's not necessary to abort the push. The checkpush call is protected by lock to prevent race on phase.

phases: properly register excluded changeset when revision are specified There was no other drawback than a bad UI message for now.

bookmarks: make -i summary simpler and more accurate

revset: allow slashes in symbols suggested by Ryan Kelly

phases: do not mark debug message for translation

templatekw: fix phase keywords

phases: fix typo in warning message

rebase: drop uppercase in abort message

largefiles: add --normal option to hg add (issue3061)

largefiles: fix caching largefiles from an aliased repo (issue3212)

run-tests: expand user in --with-hg This makes it possible to run: $ ./run-tests.py --with-hg=~/hg-bin/hg

tests: let run-tests.py default to use 'sh' in $PATH instead of '/bin/sh' This makes it easier to run tests on systems that have a usable sh in the search path but not in the standard location.

tests: add 'set -x' to the .t sh scripts in run-tests.py debug mode This makes -d output much more readable when debugging the test framework or very strange test failures.

bookmarks: clarify help for -i/--inactive

revset: fix typo in message

merge default into stable for 2.1 code freeze

revset: add remote() predicate to lookup remote revisions

bookmarks: automatically advance bookmark on naked update (BC) (issue2894)

qimport: back out 2eec74d7ce95 This patch presumed mq csets must always be secret, which isn't yet established.

phases: only synchronize on common changeset when push fails If push failed we should not expect the pushed changeset to exist on remote. The common set before the push is used for phase related operation instead of common + missing. Note: * We still pull phase data even if push fails * We still try to push data even if push fails (same than bookmark)

discovery: diet discovery.prepush from non-discovery code The ``discovery.prepush`` function was doing multiple things not related to discovery. This changeset move some code into the ``localrepo.push`` method. The old ``discovery.prepush`` function jobs is now restricted to checking for multple head creation. It was then renamed ``discovery.checkheads``. This new ``discovery.checkheads`` function may receive several other changes in the future but we are a bit too much near the freeze for a wider refactoring.

qfinish: set all qfinished patch as draft, not only qbase Fix a silly bug.

largefiles: test and simplify empty directory removal in remove

tag: invalidate tag cache immediately after adding new tag (issue3210) New tags were written to .hgtags / .hglocaltags without updating or invalidating the localrepo cache. Before afd459933d5f a lock was acquired soon after the new tags had been written, and that invalidated the cache so the new tags for example could be seen in pretxncommit hooks. With afd459933d5f the lock had already been acquired at this point and the missing cache invalidation was exposed. The tag caches will now explicitly and immediately be invalidated when new tags are added.

mq: ensure mq changesets are set to secret when no phase data are found