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.

color: use ui.formatted() to test TTYness, not sys.stdout.isatty() This fixes the color extension not working with pager (broken in 877390020477). The pager extension already sets ui.formatted=True to allow this use case.

pushkey: add hooks for pushkey/listkeys

test-patchbomb.t: clean up progress tests

util: really drop size from readfile

util: add readfile() & writefile() helper functions These two functions allow quickly reading or writing a file, without relying on reference counting to close the file handle afterwards.

revset aliases

opener: add read & write utility methods The two new methods are useful for quickly opening a file for reading or writing. Unlike 'opener(...).read()', they ensure they the file is immediately closed without relying on CPython reference counting.

dispatch: handle IndexErrors

color: verify stdout is a tty before using curses Without this change, curses complains when invoked in certain contexts because stdout isn't a tty (such as emacs integration) but we ask it to check for various bits of information from terminfo.

http: minor tweaks to long arg handling x-arg -> x-hgarg replace itertools.count(1)

httprepo: long arguments support (issue2126) Send the command arguments in the HTTP headers. The command is still part of the URL. If the server does not have the 'httpheader' capability, the client will send the command arguments in the URL as it did previously. Web servers typically allow more data to be placed within the headers than in the URL, so this approach will: - Avoid HTTP errors due to using a URL that is too large. - Allow Mercurial to implement a more efficient wire protocol. An alternate approach is to send the arguments as part of the request body. This approach has been rejected because it requires the use of POST requests, so it would break any existing configuration that relies on the request type for authentication or caching. Extensibility: - The header size is provided by the server, which makes it possible to introduce an hgrc setting for it. - The client ignores the capability value after the first comma, which allows more information to be included in the future.

store: rename the 'opener' argument to 'openertype' The 'opener' argument wasn't, in fact, an actual opener instance, but rather something expected to return an opener. The normal argument, from localrepository, is the scmutil.opener type; hence 'openertype'.

statichttprepo: make the opener a subclass of abstractopener