util & scmutil: adapt read/write helpers as request by mpm

store: use a subclass, not a function for fncacheopener

util.termwidth: never return 0 for terminal width Catch a case where the termwidth was being reported as 0 when I was connecting with TLMTask instead of NSTask in OSX. This caused the progress extension to print no progress. The termwidth should never return 0 so in case we would return 0, simply fall back to the default termwidth below which is 80.

discovery: add new set-based discovery Adds a new discovery method based on repeatedly sampling the still undecided subset of the local node graph to determine the set of nodes common to both the client and the server. For small differences between client and server, it uses about the same or slightly fewer roundtrips than the old tree-based discovery. For larger differences, it typically reduces the number of roundtrips drastically (from 150 to 4, for instance). The old discovery code now lives in treediscovery.py, the new code is in setdiscovery.py. Still missing is a hook for extensions to contribute nodes to the initial sample. For instance, Augie's remotebranches could contribute the last known state of the server's heads. Credits for the actual sampler and computing common heads instead of bases go to Benoit Boissinot.

debugbuilddag: use memctx for speed This drops the options to run arbitrary shell commands within commits and the option to create a file that gets appended to in every revision. It now supports to not write file data at all, which is very fast for generating a pure 00changelog.i (useful for discovery tests, for instance). Timings for 1000 linear nodes: * Old `hg debugbuilddag -o '+1000'` took 4.5 secs. * New `hg debugbuilddag -o '+1000'` takes 2 secs. * New `hg debugbuilddag '+1000'` takes 0.8 secs. (The last one creates only 00changelog.i).

localrepo: reuse parent manifest in commitctx if no files have changed This speeds up the in-memory version of debugbuilddag that I'm working on considerably for the case where we want to build just a 00changelog.i (for discovery tests, for instance). There are a couple of test changes because node ids in tests have changed. The changes to the patch names in test-mq-qdelete.t were required because they could collide with nodeid abbreviations and newly actually do (patch "c" collides with id "cafe..." for patch "b").

bundlerepo: fix and improve getremotechanges Fixes the regression where incoming could show local changes introduced by rev 72c84f24b420.

hgrc.5: mention new 'case collision' handling for ui.portablefilenames

win32: remove obsolete bookmarks and parentrevspec extensions from mercurial.ini

bundlerepo: drop struct

bisect: fix indent level

share: create 'hgrc' using an opener, like clone

backout 3a3584967a93 - the "unreachable code" was apparently not unreachable All tests repeatedly passes with 3a3584967a93 on some machines, but on other machines it regularly causes failure in test-mv-cp-st-diff.t, such as: @@ -203,6 +203,7 @@ - working to root: --rev 0 M a + M x/x A b a

merge with mpm

revset: avoid over-aggresive optimizations of non-filtering functions (issue2549) When limit, last, min and max were evaluated they worked on a reduced set in the wrong way. Now they work on an unrestricted set (the whole repo) and get limited later on.

convert: handle invalid subversion source paths

convert: also catch missing revlogs when introduced in repo roots The previous behaviour was almost as if convert.hg.ignoreerrors was always set for revisions without parents, except that errors were silently ignored. Revlog errors are handled as a side effect of getcopies(), but getcopies() was only called when convert.hg.ignoreerrors was set. Now we always call self.getcopies for root revisions, not only when convert.hg.ignoreerrors is set, just like we do on all other revisions. The extra call might be a bit expensive, but the proper fix for that would be to catch these errors in another way.

status: remove unreachable code for status between revisions The manifest value of a file will never be false when "not parentworking", and the expensive content comparision would thus fortunately never be reached. (If it was reached it would be wrong for example in case of renames.) This code once handled status against working directory, but that has been done elsewhere for a long time.

httprepo: proper handling of invalid responses without content-type (issue2019) This can currently be tested on http://sf.net/

httprepo: use the original exception after falling back to static-http failed Before the fine exception handling in httprepo was never shown. The static-http exception will now only be shown when static-http is requested explicitly.

test: test that backslash is preserved by the url class

tests: use raw string for url tests of '\' handling

color: fix using multiple effects

unbundler: separate delta and header parsing Add header parsing for changelog and manifest (currently no headers might change for next-gen bundle).

changegroup: new bundler API

bundlerepo: port to new bundle API

bundler: make parsechunk return the base revision of the delta

tests: add pyflakes checking for unused imports

remove unused imports

scmutil: introduce casecollisionauditor and cleaning up portability functions

check-code: check for repo in revlog and ui in util

check-code: allow for checking multiple pattern sets per file

check-code: adding debug flag

run-tests: add flag to provide extra hgrc options for test runs

graphlog: always sort revisions topologically The grapher cannot really handled revisions if they are not emitted in topological order. The previous 'reverse()' revset was not enough to achieve that and was replaced by an explicit sort call for simplicity. The --limit option is now also handled as usual with cmdutil.loglimit() instead of a 'limit' revset.

graphlog: take the union of --rev specs instead of the intersection

graphmod: correctly emit nodes with more than 2 predecessors The grandparent() function was returning only the closest predecessor of a missing parent while it must return all of them to display a correct ancestry graph.

graphlog: display nodes with more than 2 predecessors While nodes with more than 2 parents do not exist in revision graphs, they do appear when you transform them by removing subgraphs while trying to preserve ancestry links. This code was borrowed from Peter Arrenbrecht <peter.arrenbrecht@gmail.com> pbranch extension.

context: provide an efficient iterator for workingctx This avoids needing to call status or build a synthetic manifest.

merge with stable

merge with nicdumz

tests: export patches only once in test-impexp-branch

tests: do not export several times the same patch/diff in test-import

tests: move rebase-keep-branch into rebase-named-branches It's not worth building a repository just to test keep branch when we can do it our bigger, other, already built repositories.

tests: move testcase from rebase-named-branches to rebase-parameters It saves us a clone of a repository.

tests: change test-rebase-parameters to use bundle/rebase.hg

tests: change test-rebase-detach to use bundle/rebase.hg

tests: simplify test-rebase-named-branches We were cloning a repo to perform a smoke test that could have been performed earlier.

tests: upgrade bundles/rebase.hg to support test-rebase-collapse Add two changesets to the scenario so that the bundle can be reused within three tests. Before: @ 5: 'F' | | o 4: 'E' |/| o | 3: 'D | | | o 2: 'C' |/ | o 1: 'B' |/ o 0: 'A' After: @ 7: 'H' | | o 6: 'G' |/| o | 5: 'F' | | | o 4: 'E' |/ | o 3: 'D' | | | o 2: 'C' | | | o 1: 'B' |/ o 0: 'A' Revisions 0-1 keep the same number/label. Others were translated by an offset of 2 (2.C -> 4.E)

tests: introduce a rebase bundle to use with rebase tests Allows saving a few seconds in test runs by not constructing over and over the same repository.

tests: create a bundle to bootstrap tests using a remote repository It should be faster to use a single common bundle instead of recreating 4 times the same repository manually.

tests: move test bundles in a bundles/ subdirectory

tests: move test-issue436 in test-dispatch where fancyopts is tested

tests: remove test-issue433 as it's covered by test-parents

tests: remove executable bits from unified tests Those files are not executable.

tests: remove test-issue322 as it's fully included in test-issue660

Added signature for changeset 3cb1e95676ad

Added tag 1.8.3 for changeset 3cb1e95676ad

merge with i18n

i18n-pt_BR: synchronized with 42d5165975ad

merge with i18n

i18n-pt_BR: minor spacing fix

i18n-pt_BR: synchronized with 3c753f9a2fbc

zeroconf: notify the Zeroconf threads when hg exits Zeroconf launches two threads in the background, and they wait on Condition objects to exit. We need to call Zeroconf.close() to release those conditions so that threads can gracefully exit. This means that an interrupt on the hg process will now gracefully propagate to the Zeroconf children, fixing that bug which did not allow us to kill an `hg serve` process.