merge with stable

run-test: fixed wrong parenthesis Fixed wrong placement of end parenthesis, from b911cb80c671

merge with crew

merge with crew

merge with stable

graphmod: safer code when a changeset has two identical parents While this situation should never under normal use, some real life repos sometimes contain such changesets (older hg versions, broken rebases, etc...) hgweb was displaying an "Internal error" in this case, and graphlog displayed a redundant branch all the way to null: it does not cost us much to just ignore this extra parent when constructing the DAG.

revlog: fix descendants() if nullrev is in revs We were not returning the correct result if nullrev was in revs, as we are checking parent(currentrev) != nullrev before yielding currentrev test-convert-hg-startrev was wrong: if we start converting from rev -1 and onwards, all the descendants of -1 (full repo) should be converted.

revlog: if start is nullrev, end is always a descendant

mq: use sets instead of lists for speed The code eventually converts data through sets to ensure unicity: do it earlier to allow faster __contains__ lookups and avoid `del l[l.index(x)]` kind of code.

context: add __repr__ methods to workingfilectx and workingctx

merge with crew

test-import: workaround for missing newline is no longer needed

merge with stable

tests: use (esc) instead of other kinds of string escaping

tests: use (esc) for all non-ASCII test output

tests: use (esc) markup for string-escape This makes test output less ambiguous. Failing test output will be escaped and marked up if necessary. A Python string-escape compatible encoding is used, but not everything is encoded - especially not \n and \t and '.

tests: (no-eol) markup for command output without trailing LF Output chunks without a trailing LF will now work but get (no-eol) appended. This change mostly moves code around so we can handle that an output line starts with data from previous command, followed by salt and the next command.

merge with stable

opener: check hardlink count reporting (issue1866) The Linux CIFS kernel driver (even in 2.6.36) suffers from a hardlink count blindness bug (lstat() returning 1 in st_nlink when it is expected to return >1), which causes repository corruption if Mercurial running on Linux pushes or commits to a hardlinked repository stored on a Windows share, if that share is mounted using the CIFS driver. This patch works around issue1866 and improves the workaround done in 50523b4407f6 to fix issue761, by teaching the opener to lazily execute a runtime check (new function checknlink) to see if the hardlink count reported by nlinks() can be trusted. Since nlinks() is also known to return varying count values (1 or >1) depending on whether the file is open or not and depending on what client and server software combination is being used for accessing and serving the Windows share, we deliberately open the file before calling nlinks() in order to have a stable precondition. Trying to depend on the precondition "file closed" would be fragile, as the file could have been opened very easily somewhere else in the program.

util: refactor opener - Don't call atomictempfile or nlinks() if the path is malformed (no basename). Let posixfile() raise IOError directly. - atomictempfile already breaks up hardlinks, no need to poke at the file with nlinks() if atomictemp. - No need to copy the file contents to break hardlinks for 'w'rite modes (w, wb, w+, w+b). Unlinking and recreating the file is faster.

revset: remove unnecessary debug statement

revset: fix p1, p2 and parents in dirstate case (a5f7f1e9340e) - Handle 'subset' argument - Stop returning the null rev from p1 and parents, as in the non-dirstate case - Order parents as in the non-dirstate case (ascending revs)

tests: handle .t files without trailing LF 9a2de8dae27b made this simple test-test.t succeed silently: $ printf ' $ true' > test-test.t but did not give a usable .err in this case: $ printf ' $ false' > test-test.t The missing LF will now be fixed in the test output and it will thus give a test failure and a solution in the .err file.

merge with stable

alias: fall back to normal error handling for ambigious commands (fixes issue2475)

merge with stable

subrepo: test & fix svn subrepo removal

revsets: let parents() return parents of working dir This patch makes the 'set' argument to revset function parents() optional. Like p1() and p2(), if no argument is given, returns the parent(s) of the working directory. Morally equivalent to 'p1()+p2()', as expected.

revsets: let p1() and p2() return parents of working dir This patch makes the 'set' argument to revset functions p1() and p2() optional. If no argument is given, p1() and p2() return the first or second parent of the working directory. If the working directory is not an in-progress merge (no 2nd parent), p2() returns the empty set. For a checkout of the null changeset, both p1() and p2() return the empty set.

util: refactor opener - Don't call atomictempfile or nlinks() if the path is malformed (no basename). Let posixfile() raise IOError directly. - atomictempfile already breaks up hardlinks, no need to poke at the file with nlinks() if atomictemp. - No need to copy the file contents to break hardlinks for 'w'rite modes (w, wb, w+, w+b). Unlinking and recreating the file is faster.

keyword: turn regexes and escaped keywords into a propertycache

commands: add revset support to most commands

convert: better ReST markup in docstring

convert: split docstring lists for easier translation

convert: use field list instead of option list in help Use field list instead of option list in convert help, because the option list format used, with defaults and type of argument is not supported by docutils.

doc/Makefile: docs now also depend on extensions After 0d09991f91ee the hg(1) manpage contains a section with help extracted from the extensions, so we should depend on them too.

keyword: function to look up changectx for expansion Similarly rename variable in kwtemplater.overwrite().

localrepo: make heads use the keyword args of the sorted builtin

import: add another line feed to message join string Changeset descriptions are not guaranteed to have a trailing carriage return.

tests: unify test-no-symlinks

patch: remove unused applydiff() sourcefile argument

patch: remove unused gitworkdone variable from iterhunks()

test-import: use printf instead of echo

import: --no-commit should update .hg/last-message.txt The patch parser goes through all of that trouble extracting the commit message from the patch file. It seems such a waste not to use it.

merge with stable after 1.7 release

Added signature for changeset 333421b9e0f9

Added tag 1.7 for changeset 333421b9e0f9

merge with i18n

i18n-pt_BR: synchronized with b19b4c1df066

dirstate: skip optimization on case-folding FS (issue2440)

url: fix https client authentication through proxy There is no tests for this, but the parameter order was obviously wrong.

merge with i18n

i18n-sv: synchronize with 13fb555677fe

i18n-zh_TW: synchronize with 15ca4bfecfe3

i18n-ja: strip extra spaces next to punctuation mark at line ending

i18n-pt_BR: synchronized with 15ca4bfecfe3

commit: handle missing newline on last commit comment

localrepo: do not modify ctx.remove() list in-place

test-rename: test with absolute paths

test-rename: fix \" -> " in comments

rebase: improve resolve failure message

run-tests: use regex when searching for $HGPORT in test output This prevents spurious errors when a changeset hash happens to match the port number. Before, this invocation gave a test failure: $ ./run-tests.py test-log.t --port 24427 ERROR: /home/mg/src/mercurial-crew/tests/test-log.t output changed --- /home/mg/src/mercurial-crew/tests/test-log.t +++ /home/mg/src/mercurial-crew/tests/test-log.t.err @@ -626,12 +626,12 @@ $ hg log -b default changeset: 2:c3a4f03cc9a7 - parent: 0:24427303d56f + parent: 0:$HGPORT303d56f user: test date: Thu Jan 01 00:00:00 1970 +0000 summary: commit on default ...

demandimport: back out 50a4e55aa278 (issue2467)

debugindex: add --format flag to allow debugging parentdelta -f 1 shows extra data from revlogv1 (aka revlogng) including flags and size (based on a patch by Pradeepkumar Gayam <in3xes@gmail.com>)

pager: make example of setting pager less silly

convert: Work around p4 instability (issue2465) The p4 command-line client sometimes fails upon doing "p4 describe" when trying to produce a patch. (I'm guessing it's a bug in p4.) However, "hg convert" doesn't even make use of the patch, and it can be elided by adding "-s" to the p4 command line here.

revlog: choose best delta for parentdelta (issue2466) When parentdelta is enabled, we choose the delta that has the minimum distance to its base. Otherwise, base may be sufficiently far away to require a full version, resulting in greatly reduced compression.

revlog: precalculate p1 and p2 revisions

revlog: extract delta building to a subfunction

revlog: simplify cachedelta handling

revlog: fix buildtext local scope buildtext stores its result in _addrevision scope to avoid repeated builds cachedelta is already visible

merge with i18n

i18n-ja: synchronized with 6f6f6a9c2a41

i18n-pt_BR: synchronized with db2ff771204d Reviewed formatting fixes from eda77c3e246a.

i18n-da: translate help for bookmarks extension

i18n, bookmarks: add comments for translators

i18n-da: synchronize with e1855dee28c1

qnew: distinguish between existing file and directory (issue2464)

qnew: give better feedback when doing 'hg qnew foo/' (issue2464)

opener: do not create "foo" directory when writing to "foo/" The directories were not cleaned up when the subsequent open failed and this would confuse things like qnew.

pager: backout 05077896ffe2 (issue2441)

mq: qrename should not touch the dirstate if src is untracked (issue2460)

patch: fix copies when patching over uncommitted changed (issue2459)

merge with i18n

i18n-pt_BR: synchronized with 830be2c57626

i18n-pt_BR: msgmerge with 830be2c57626

merge with i18n

i18n-da: remove extra newline in translation

i18n-da: synchronize with 6137c5bba4d0

minirst: use colwidth to match title lengths (issue2455)

encoding: default ambiguous character to narrow The current implementation of colwidth was treating 'A'mbiguous characters as wide, which was incorrect in a non-East Asian context. As per http://unicode.org/reports/tr11/#Recommendations, we should instead default to 'narrow' if we don't know better. As character width is dependent on the particular font used and we have no idea what fonts are in use, this recommendation applies. This introduces HGENCODINGAMBIGUOUS to get the old behavior back.

*: kill all unnecessary shebangs.

*: add executable bit to a few files that were missing it.

log: do case insensitive search for --user option

url: show realm/user when asking for username/password

rebase: abort message should appear even with --quiet