store: optimize _auxencode() by assigning to the list elements of the path

store: optimze _auxencode() a bit by grouping the reserved names by length This reduces perffncacheencode wall time on Windows 7 x64 for my netbeans clone here from 4.3 to 4.0 (7% faster).

store: explain "aux.foo" versus "foo.aux" in doc of _auxencode()

store: add 'com0' and 'lpt0' doctest cases for _auxencode() These are already covered by test-hybridencode.py, but they are so noteworthy that I think they deserve being shown right in that doctest.

wireproto: fix check-code.py breakage introduced by 6d97dd630d79

record: fix display of non-ASCII names in chunk selection b013baa3898e fixed display of non-ASCII names in file-selecting prompt, but display in chunk selection remained broken. The reason is that using '%r' in string formatting results in calling `repr` on file names, thus mangling non-ASCII ones.

tests: enable even more Windows server tests

test-obsolete-checkheads: fix on windows

sshserver: avoid a multi-dot attribute lookup in a hot loop This improves stream_out performance by about 3%.

store: reduce string concatenation when joining This improves stream_out performance by a couple of percent.

scmutil: use the new faster path split Combined with a few other patches in this series, this contributes to improving stream_out performance by 10%.

util: implement a faster os.path.split for posix systems This is not yet used.

scmutil: make join cheaper Combined with a few followup patches, this contributes to improving stream_out performance by 10%.

wireproto: don't format a debug string inside a hot loop This improves stream_out performance by about 5%.

wireproto: bypass filechunkiter for small files when streaming Merely creating and using a generator has a measurable impact, particularly since the common case for stream_out is generators that yield just once. Avoiding generators improves stream_out performance by about 7%.

wireproto: don't audit local paths during stream_out Auditing at this stage is both pointless (paths are already trusted by the local repo) and expensive. Skipping the audits improves stream_out performance by about 15%.

scmutil: delegate mustaudit property to the real opener This will be used by an upcoming patch.

scmutil: turn opener._audit into a property, mustaudit This will be used by an upcoming patch.

perf: add perffncacheencode Examples (all done with somewhat dated clones I found on my disk): Netbeans (~120k entries in fncache): $ hg perffncacheencode ! wall 4.338000 comb 4.336828 user 4.336828 sys 0.000000 (best of 3) Openoffice (~77k entries in fncache)): $ hg perffncacheencode ! wall 1.533000 comb 1.528810 user 1.528810 sys 0.000000 (best of 7) Xen (~10k entries in fncache): $ hg perffncacheencode ! wall 0.198000 comb 0.187201 user 0.187201 sys 0.000000 (best of 51) Done on Windows 7 x64.

Merge with mpm

bookmark: take successors into account when updating (issue3561) When we rewrite a bookmarked changeset, we want to update the bookmark on its successors. But the successors are not descendants of its precursor (by definition). This changeset alters the bookmarks logic to update bookmark location if the newer location is a successor of the old one[1]. note: valid destinations are in fact any kind of successors of any kind of descendants (recursively.) This changeset requires the enabling of the obsolete feature in some bookmark tests.

bookmarks: extract valid destination logic in a dedicated function We usually update bookmarks only if the new location is descendant of the old bookmarks location. We extract this logic into a function. This is the first step to allow more complex logic using obsolescence in this validation of the bookmark movement.

checkheads: don't warn about unsynced changes that we ill obsolete We won't be able to pull them after this push.

checkheads: check successors for new heads in both missing and common A relevant obsolete marker may have been added -after- we previously exchanged the changeset. We have to search for remote heads that disappear by the sole fact of pushing obsolescence. This case will also happen when remote got the new version from a repository that does not propagate obsolescence markers.