hgweb: make PATH_INFO handling slightly more robust

Merge with crew

Merge with crew-stable

Merge with crew-stable.

Merge with stable

minor typo fix in templater's docstring

Add test for issue 529 - "mq aborts when merging patch deleting files".

mq: don't abort when merging a patch that removes files

atomicfile: don't copy the original file if it'll be truncated

use atomictemp files to write the dirstate

use atomictemp files to write branch.cache

util.opener: if requested, use atomicfile even if the file doesn't exist Right now, surprisingly enough, if you request an atomic file but the file still doesn't exist, you get a regular file. AFAICS, the only time this happens is during the initial creation of the dirstate.

cache os.umask even on windows

pull umask-checking up

Merge with crew-stable.

help: log --keyword is case-insensitive

hgweb: expand keyword search to full list of files

log: expand keyword search to full list of files

run-tests.py: use coverage.py with "#!/usr/bin/env python" tests

run-tests.py: small cleanup

run-tests.py: use coverage.py with *.py tests

run-tests.py: tell coverage.py to ignore errors Otherwise there'll be some IOErrors when it tries to open python files created during the execution of e.g. test-hook.

test-bad-pull: try to avoid timing-related failures

Try to find diffstat in PATH before calling it At least on Solaris, /bin/sh will print a "command not found" message even if we redirect stderr.

Add a pointer to "hg -v help" to the bottom of hg help {,cmd} output This should make it easier to discover global options. As a bonus, they are no longer displayed by something like a hg -v help dates

revlog.py: fix/tweak read ahead code in lazyparser

Merge with Matt

Merge with Matt

Move back the purge extension in hgext

purge: abort with missing files avoiding problems with name-mangling fs In a name mangling filesystem (e.g. a case insensitive one) dirstate.walk() can yield filenames different from the ones stored in the dirstate. This already confuses the status and add commands, but with purge this may cause data loss. To prevent this purge refuses to work if there are missing files and has a 'force' option if the user knows it is safe. Even with the force option purge checks if any of the missing files is still available in the working dir: if so there may be some problem with the underlying filesystem, so it unconditionally aborts.