i18n-pt_BR: synchronized with 4e7149ed98e8

merge with i18n-stable

Merge with -stable

color: allow multiple args to ui.write()

color: add support for record extension

util: move rename into posix.py and windows.py

util: state docstring of rename more precisely

cmdutil: changeset_printer: use methods of filectx/changectx. This allows extensions that modify changeset metadata (e.g. description) by overriding methods of changectx to get consistent behavior from all log-like commands, regardless of whether templates or styles are used. Without this, overriding changectx methods works if you use styles or templates, but not with default log format. This meant adding filectx.extra() for consistency with changectx.

Merge with crew-stable

verify: detect file copy sources not in parents with --verbose

Merge with crew-stable

convert/cvs: stop supporting external cvsps

Merge with crew-stable

Merge with crew-stable

help: un-indent help topics The help topics are reused in the HTML documentation, and there it looks odd that whole sections are indented. We now only indent it for output on the terminal.

help: move help topics from mercurial/help.py to help/*.txt The help topics are loaded on demand so we wont hit the disk unless we really have to.

i18n: remove unnecessary os.path.normpath call

commands: simpler sort of help topic names

cmdutil: templating keywords latesttag and latesttagdistance This can be used for referring to revisions in a reasonable meaningful, stable and monotonically increasing way, suitable for releases or builds directly from a repository. The latest tag is found by searching through untagged ancestors and finding the latest tagged ancestor based on tag date. The distance is found from the length of the longest path to the tagged revision. For example: hg log -l1 --template '{latesttag}+{latesttagdistance}\n' can return 1.3.1+197 This is mostly work by Gilles Moris <gilles.moris@free.fr>

merge with mpm

bdiff: gradually enable the popularity hack Patch from Jason Orendorff The lower the threshold, the stronger the popularity hack's influence. So at 3999 lines, the hack is disabled; and at 4000 lines, the hack is enabled at maximum strength (t=4). No source file in mercurial/crew is over 4000 lines. But there are, oh, a few such files in Mozilla. I can testify that this hack causes hg to generate some correct but eyebrow-raising patches. I think the hack should phase in gradually. The threshold should be high for small files where we don't need it so much. Like this: t = (bn < 31000) ? 1000000 / bn : bn / 1000; That would leave the popularity hack disabled for small files, then gradually phase it in: bn < 1000 -- t > bn (popularity hack is completely disabled) bn == 1000 -- t = 1000 (still effectively disabled) bn == 2000 -- t = 500 (only hits unusual files) bn == 10000 -- t = 100 (only hits especially common lines) bn == 31000 -- t = 31 (hack is at maximum power) bn == 32000 -- t = 32 (hack could backfire, ease off)

Merge with -crew-stable

convert/hg: handle bogus copy records (issue1843)

convert/hg: make parents() return changectx, not nodes

Merge with -crew-stable

util.rename: do not abort if os.unlink fails (issue1840)

convert: make mapfile handle LF and CRLF shamap (issue1846)

convert/darcs: handle directory renaming

convert/darcs: fix file renaming (issue1853)

Fix failing darcs test