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