test-fetch: fix non-portable sed regex. (s/...\+/.../ appears to be a GNU-ism: this test broke on OS X and NetBSD. Changing \+ to * fixes it, although that is a slightly less strict regex.)

branch heads: optimise computation of branch head cache (issue1734) The previous branch heads cache implementation iterated all ancestors for each new revision in the repository, causing a massive slowdown on cloning larger repositories.

Merge with stable

cmdutil: fall back to filename if glob expand has errors On Windows, Mercurial tries to glob expand provided filenames as a convenience to the user. Unfortunately, there are valid filenames which are not valid glob patterns. In those cases, we should fallback to the original provided filename.

inotify: server: explicitely ignore events in subdirs of .hg/ (issue1735)

inotify: fix issue1375, add a test. The biggest problem was the data structure, which did not allow changing a file into a directory or vice versa. This problem is fixed by b55d44719b47. The walk() method also had an issue in this case: - we know 'path' as a directory. inotify server sleeps. - 'path' is deleted - 'path' is recreated as a file - the server catches up here, and see the deletion. it instantiates a scan(), which in its turn calls for walk(repo, path). - walk() then assumes that 'path' is a directory and calls os.listdir on it, which raises an OSError(errno.ENOTDIR) Catch the error, and yield the file instead of the directory contents.

inotify: server: new data structure to keep track of changes. == Rationale for the new structure == Current structure was a dictionary tree. One directory was tracked as a dictionary: - keys: file/subdir name - values: - for a file, the status (a/r/m/...) - for a subdir, the directory representing the subdir It allowed efficient lookups, no matter of the type of the terminal leaf: for part in path.split('/'): tree = tree[part] However, there is no way to represent a directory and a file with the same name because keys are conflicting in the dictionary. Concrete example: Initial state: root dir |- foo (file) |- bar (file) # data state is: {'foo': 'n', 'bar': 'n'} Remove foo: root dir |- bar (file) # Data becomes {'foo': 'r'} until next commit. Add foo, as a directory, and foo/barbar file: root dir |- bar (file) |-> foo (dir) |- barbar (file) # New state should be represented as: {'foo': {'barbar': 'a'}, 'bar': 'n'} however, the key "foo" is already used and represents the old file. The dirstate: D foo A foo/barbar cannot be represented, hence the need for a new structure. == The new structure == 'directory' class. Represents one directory level. * Notable attributes: Two dictionaries: - 'files' Maps filename -> status for the current dir. - 'dirs' Maps subdir's name -> directory object representing the subdir * methods - walk(), formerly server.walk - lookup(), old server.lookup - dir(), old server.dir This new class allows embedding all the tree walks/lookups in its own class, instead of having everything mixed together in server. Incidently, since files and directories are not stored in the same dictionaries, we are solving the previous key conflict problem. The small drawback is that lookup operation is a bit more complex: for a path a/b/c/d/e we have to check twice the leaf, if e is a directory or a file.

merge with crew-stable

gitweb, monoblue: fix double-spacing in file view (issue1733) The error was introduced in 338412820a57.

util: use propertycache in opener instead of __getattr__

mq: use ui.status when pushing and popping patches

mq: qpop now tells which patches are popped When navigating through a patch series by qpushing and qpopping it was easy to get lost because qpop was silent. I found myself often running qnext after qpop to see which patch I just dropped - especially if I was about to qrm it. This patch makes qpop more symmetric to qpush by showing which patches are applied/"unapplied". I think it is a good change even though it changes output by adding a new line of output.

merge with crew-stable

url: fix use of non-int port in https connections (issue1725) Versions of Python before 2.6 cannot automatically convert a given port number to an integer, so we add a conversion to coerce the given input to an int.

doc/Makefile: let hg1.gendoc.txt depend on gendoc.py

keyword: use all caps for 'note:' in help string The diff, export, log, and status commands write it as 'NOTE:'.

notify: fix indentation in module docstring

notify: cleanup module docstring

convert: fix inconsistent indentation in help text The sort modes flags and convert.cvsps options were indented while the convert.hg, convert.svn, and convert.p4 options were not. I've now un-indented all of them.

Merge with stable

filectx: add a hex method

win32mbcs: also wrap windows.pconvert()

Use os.path.split() for MBCS with win32mbcs extension.

win32mbcs: look up modules using sys.modules (issue1729) globals()[module] doesn't work for modules inside of packages, such as os.path.

fix memory usage of revlog caches by limiting cache size [issue1639]

keyword: eliminate potential reference cycles from kwrepo - delete kwrepo.commitctx after using the tweaked version - prefer self.hook over repo.hook to avoid nesting Also pass arguments to commit as arbitrary list. Thanks to Simon Heimberg and Matt Mackall for guidance.

convert/cvs: improve error message on unexpected server output.

transaction: fix uncaught ENOENT (issue1724) The opener raises an IOError on errors where transaction expects an OSError.

branch heads: fix regression introduced in e67e5b60e55f (issue1726) For merge nodes it is not adequate to only check a single possible branch head for whether it is an ancestor of the latest head, but it needs to be done for each possible branch head.

subrepo: use hg.repository instead of creating localrepo directly this way, extensions' reposetup will be called, which allows for git subrepos to be handled by hg-git (and I believe the same goes for svn and hgsubversion)

ignore: separate pattern extraction from match compilation hgignore files have slightly different syntax from match objects, e.g. syntax: foo headers, regexp: forms, and re being relre. Put conversion from hgignore syntax into match syntax into a standalone function so that it is easier to validate hgignore hunks externally.

merge with crew-stable

util: remove unused bufsize argument Removed it correctly this time: the subprocess default is 0, not -1 and so we must pass -1 explicitly. Added a comment to that effect.

convert/cvs: improve error message on unexpected server output.

typos: "it's" -> "its"

convert: fixed typo in docstring

Merge OS X performance regression fix

Merge backed out change

Backed out changeset fce065538bcf: it caused a 5x performance regression on OS X

help: wrapped help strings at 78 characters

keyword: collect kwmaps using a generator expression Allowed for Python 2.4.

commands: avoid bad linebreak in addremove docstring

Makefile: wrap hg.pot strings at 82 chars By default, xgettext will wrap strings at 79 characters. This width includes the two double-quotes and the '\n' added. Our strings are now wrapped at 78 characters and a line can therefore be up to 82 characters wide in the .po file. Setting the width to 82 characters ensures that xgettext does no silly wrapping on our already-wrapped strings while still wrapping long one-liners at 82 characters.

zeroconf: wrapped docstrings at 78 characters

win32mbcs: wrapped docstrings at 78 characters

transplant: wrapped docstrings at 78 characters

share: wrapped docstrings at 78 characters

record: wrapped docstrings at 78 characters

rebase: wrapped docstrings at 78 characters

purge: wrapped docstrings at 78 characters

patchbomb: wrapped docstrings at 78 characters

parentrevspec: wrapped docstrings at 78 characters

pager: wrapped docstrings at 78 characters

notify: wrapped docstrings at 78 characters

mq: wrapped docstrings at 78 characters

keyword: wrapped docstrings at 78 characters

interhg: wrapped docstrings at 78 characters

highlight: wrapped docstrings at 78 characters

hgk: wrapped docstrings at 78 characters

hgcia: wrapped docstrings at 78 characters

graphlog: wrapped docstrings at 78 characters

fetch: wrapped docstrings at 78 characters

extdiff: wrapped docstrings at 78 characters

convert: wrapped docstrings at 78 characters

color: wrapped docstrings at 78 characters

churn: wrapped docstrings at 78 characters

children: wrapped docstrings at 78 characters

bugzilla: wrapped docstrings at 78 characters

bookmarks: wrapped docstrings at 78 characters

acl: wrapped docstrings at 78 characters

commands: wrapped docstrings at 78 characters We have always had a left margin of 4 characters -- probably just because that's how docstrings for top-level functions turn out by default, but it also looks nice in the built-in help. The docstrings were wrapped at 70 characters, which is the default for Emacs. However, this gives a right margin of 10 characters in a standard 80 character terminal. I've now wrapped the relevant docstrings at 78 characters, effectively killing the right margin. The asymmetric margins looked a bit odd and some of the text looked cramped with a right margin, so Dirkjan and I felt that it was best to remove it entirely. The two character gap was kept to have some space between the border of the terminal -- it will also make diffs involving the docstrings fit in a 80 character line.

extdiff: fix indentation and use gettext

filemerge, subrepo: correct indention

ui: extract choice from prompt avoid translating single characters (as l for _local or sym_link)

patchbomb: use local time for the Date: header

patchbomb: fix From_ in the message's envelope Localized date in the From_ prevents MUAs like mutt from parsing mbox files generated by patchbomb. Using a 24 characters date in asctime format instead.

merge with crew-stable

Bourne shells do not maintain $PWD; update tests accordingly

tests: remove more instances of export FOO=bar bashism

tests: remove more instances of export FOO=bar bashism

test-gpg: suppress secure memory warning Some platforms (Solaris for one) does not support secure memory and would give a warning.

test: fix for compatibilty with true Bourne /bin/sh 'export foo=bar' is an extension, replaced with 'foo=bar; export foo'

p4: simplify sort key

localrepo: removed unnecessary revkey sort helper

compat: remove unnecessary diamond-shaped multiple inheritance

split local and stdlib module imports (eases migration issues)

compat: don't reference an exception var inside a lambda

compat: use email in favor of mimetools

verify: fix scope issues with del statement

compat: use 'key' argument instead of 'cmp' when sorting a list

compat: use open() instead of file() everywhere

compat: can't compare two values of unequal datatypes

compat: use // for integer division

tests: add -3 switch to run-tests.py

keyword: remove unused import

merge with crew-stable

help: add #revision syntax to the example valid URLs.

context: improve arg-checking assert.

help: add #revision syntax to the example valid URLs.

merge wtih crew-stable

gendoc: fix localization of help topic When a topic provides a callable method for its text, most likely this text will be generated from different parts, so it does not make sense to apply gettext on the whole result, rather the method should provide translation by itself. This is the case with the extensions topic, which triggers a double gettext call, making the ASCII codec fail when it encounters 8 bit characters, and prevents the documentation from being built.

extensions: remove dead code enabled used to be a boolean, and somehow that bit of code inadvertently slipped through during a refactoring. Effectively dead code, as the condition can never be triggered.

merge with crew-stable

acl: read correct index into url for username (issue298) The index was inadvertedly off-by-one causing the username to be the remote host rather than the remote user when hosted in a http(s) session.

color: don't highlight the summary part of the qseries command

mq: align columns in verbose qseries output.

extensions: remove unused imports

test python hook configured with python:[file]:[hook] syntax Adds a test for python hooks configured with python:[file]:[hook] syntax in .hgrc. Increases the test coverage for mercurial/hook from 92% (79/85) to 96% (82/85).

keyword: break overlong line

bisect: fix format specifiers for integers

Added signature for changeset 196d40e7c885

Added tag 1.3 for changeset 196d40e7c885

Merge with i18n

i18n-pt_BR: synchronized with 59bb11a97fe5

i18n-jp: translation update for 09c6735e3880

i18n-fr: translation of part of the mq extension

i18n-fr: translation of the zeroconf extension

i18n-fr: translation of the purge extension

i18n-fr: translation of the parentrevspec extension

i18n-fr: synchronized with 7d39c76be4ee