Renamed "manifest" to "files" in web templates. manifest.tmpl is still used, so people having their own templates don't have to change them. "cmd=manifest" still works, new style URLs are not affected, because they already used "/file/".

Removed old-style hgweb templates

add explicit extension disabling syntax to hgrc.5

Permit XML entities to be escaped in template output. Useful for creating XML documents directly from Hg logging. Can also be used for HTML. For use in content, will escape '&', '<', and for completeness '>' (although it is not strictly necessary). For use in attributes, will also escape ' and ". Will also replace nonprinting (ASCII) control characters with spaces, since these are illegal in XML.

convert: add shallow, single branch svn conversions via svn.startrev

convert: allow svn trunk/branches/tags detection to be skipped - eluding convert.svn.branches defaults to "branches" - convert.svn.branches= disables branches detection - convert.svn.branches=/ is equivalent to former convert.svn.branches=

Add --all option to bundle command

Fix test-convert.out after 55455556f921

convert: improve subversion source documentation

hgweb: fix parameter mixup (issue1001)

tests: easier hg serve error diagnosis

util: make walkrepos() return .hg/patches if present

Allow "file://localhost/" in addition to "file:///" (issue728) file://localhost/ URLs are generated by Mac OS X API calls like [NSURL fileURLWithPath:]. Imported patch from Paul Bx.

mq: make qclone ask remote source repo for qbase using lookup protocol

Document log date ranges and mention 'hg help dates' for all commands (issue998)

Add test case for backout on named branches (issue665)

Reverse the way backout is doing the merge Currently, backout is creating a backout revision as a child node of the backed out node and will leave you at this new head. This has several drawbacks: * this changes the current head * when there is a long history between the backed out node and the current head, this will generate a huge number of diffs that are scary at first sight, and not very natural to review before commit. The change consists to switch back to the original node as soon as the backout node (which becomes the new tip) has been created. Then the --merge option can just merge this new tip in the current node. * the current head/node is not changed from the user's point of view * even without using the --merge option, the backout revision is still easy to locate, as this is the tip * the merge is much more intuitive as diffs of the merge is right you are looking to backout

tests: hide the name of the branch cache file

test-mq-pull-from-bundle: don't print the contents of $HGRCPATH

repo.status: also compare flags for files in the lookup list. We might be able to do something smarter about this in dirstate.status for files in normallookup state, but that would require some extra care to keep backwards compatibility.

keyword: remove "identify" and "remove" from nokwcommands These two commands care about the list of modified files returned by repo.status and we may need to do a full content comparison to populate that list.

test-glog: pass the list of files to commit test-glog uses debugsetparents instead of update+merge to create some funky DAGs, and so the dirstate contents won't be consistent with the checked out revision. Passing an explicit list of files to commit reduces a bit the dependency on the dirstate. Using a non-deprecated rawcommit might be better here.

hgweb: no i18n in protocol responses

improve changegroup.readbundle(), use it in hgweb

Also search for .hgrc if mercurial.ini not found on windows

hgweb: use bundletypes from mercurial.changegroup

Merge with crew

Infer a --repository argument from command arguments when reasonable. In particular: if invoked without -R from a CWD not inside a repo, having been passed one or more file paths as command arguments, where the nearest enclosing repo of all of those paths is the same, quietly infer a -R option for that repo. Otherwise abort with an error message as before.