mq: do not allow to push from repo with patches applied

call reposetup functions of extension modules whenever repo created

mq: test commit in repo with patches applied

Disallow commit over an applied mq patch.

qselect: add --pop, --reapply options

Fix some tests for portability.

merge: minor simplification

Remove manifest.readflags

Change remaining users of manifest flags

Switch to simpler manifestdict

Merge: use single objects for tracking manifests

Merge: save away mode bit so that we don't need manifest later

Merge manifest refactor work

Combine manifest dict and flags dict into a single object This gets rid of the need to track two objects and might save memory. This might be faster implemented as a subclassed dict with auxiliary functions to access a sparse flags dict.

manifestflags: eliminate remaining users of direct dict access

Use strings for manifestflags to allow storing multiple flags

Start using manifestflags methods

Add manifestflags class

Merge with crew, fix most tests

mq: make guards more strict, add tests

mq: drop qversion command

fetch: hold lock and wlock across all operations

tests: forgot to add test-mq-guards.out

fetch: lock repo across pull and commit

fetch: drop commands.doupdate

test-fetch: make output stable

fetch: fix breakage from mpm. add test so will not break again.

mq: new commands qselect, qguard implement quilt-style guards for mq. guards allow to control whether patch can be pushed. if guard X is active and patch is guarded by +X (called "posative guard"), patch can be pushed. if patch is guarded by -X (called "nagative guard"), patch cannot be pushed and is skipped. use qguard to set/list guards on patches. use qselect to set/list active guards. also "qseries -v" prints guarded patches with "G" now.

fix permission of test-mq-qsave

mq: add join method

Make mq camelcase consistent with the rest of hg.

Add basic qsave/qrestore test.