fix warning from pychecker

fix error spotted by pychecker

Merge with crew-stable

commands: fix shadowed repo module

merge with crew

hgweb: remove dead code

Merge with crew-stable

test-convert-svn-source: remove redundant tests

convert: allow tags detection to be disabled Tags calculation becomes more reliable but slower, measurable on frequent synchronizations.

convert: follow svn tags history (issue953)

Add a test for svn tags conversion

convert: avoid svn log retrieval process cleanup With huge history (like kdelibs), the process termination suddenly consumes a lot of memory (from 700M to 1.3G+). Since the job is done, clean termination is not required, just exit.

test-convert-mtn: test directory deletion

fix const annotation warning

highlight: some small cleanups

hgweb: refactor hgweb code

hgweb: separate out utility functions

Backed out changeset d2bb66a8a435 (temporary template compatibility)

mercurial.el: note new Emacs VC mode support

manifest: improve parsing performance by 8x via a new C extension

Added signature for changeset bae2e9c838e9

Added tag 1.0 for changeset bae2e9c838e9

Tests for issue 1049

commit: when committing the results of a merge, it's all or nothing Previously, it was possible to commit just one file from a merge, which is essentially always the wrong thing to do. This fixes issue 1049.

Skip older monotone versions for tests. test-convert-mtn is known to work with 0.37 and 0.38, but fails with 0.31 (Debian etch). hghave now skips all versions up to 0.31.

run-tests.py: Only one fail message when output changed and error code. This fixes passing back fail messages mistaken for skip messages when running with parallel jobs because run_children() only expects one message per fail.

mq: use repo.changelog.tip() instead of the "tip" tag

Fix missing space in one of the new update messages.

qclone: do not abort if remote hasn't enabled mq (issue1040)

hgweb: add compatibility code for old templates Up to changeset 3340aa5a64f7, HTTP headers were expected to be embedded in the "headers" template. Since that changeset, the content-type is supposed to be defined as the "mimetype" template in the map file. This changeset makes sure the old templates still work.