help: add/fix docstrings for a bunch of extensions

extensions: simplify by selecting primary hgext

extensions: move extensions listing functions from mercurial.help Includes some small fix-ups to comments in enabled() and disabled().

serve: obey the --encoding option

contrib/buildrpm: Don't require installed hg, use local hg with pure extensions

contrib/buildrpm: Don't use perl

contrib/buildrpm: Support python 2.4 and 2.6

help: remove per-extension paragraph on how to enable it The central place to find this information is the "extensions" help topic.

help: expand the extensions topic

help: refactor extensions listing, and show enabled ones in the dedicated topic

help: adding a new help topic about extensions Currently listing non-enabled extensions and a short introductory text. Thanks to Dan Villiom Podlaski Christiansen for the preliminary proof-of-concept code for listing available extensions.

bookmarks: add appropriate locking (issue1691) - make updates of bookmark state locked and atomic - wrap commit so that commit and bookmarks happen under the same lock

filemerge: fix internal:dump

hgweb: deny cloning a subpath of a repo

hgweb: web.encoding should override encoding.encoding (issue1183)

bdiff: fix compile with GCC -ansi (issue1690)

tags: silence warning about unknown tags This is mostly a nuisance and can happen legitimately with pull -r, etc.

rollback: minor clarification (issue828)

update: add --check option

tags: drop nested function

tags: generate contexts directly

tags: reverse and simplify head-walking

tags: simplify rev handling

tags: fold in _hgtagsnodes

compare grep result between target and its parent I found that typical case is that grep target is added at (*) revision in the tree shown below. +--- 1(*) --- 3 0 +--- 2 ------ 4 Now, I expect 'hg grep --all' to show only rev:1 which is first appearance of target line. But 'hg grep --all' will tell: target line dis-appeared at 3 => 4 target line appeared at 2 => 3 target line dis-appeared at 1 => 2 target line appeared at 0 => 1 because current 'hg grep' implementation compares not between target revision and its parent, but between neighbor revisions in walkthrough order. I checked performance of this patch by "hg grep --follow --all walkchangerevs" on whole Mercurial repo, and patched version could complete as fast as un-patched one.

url: let host port take precedence when connecting to HTTPS Fixes use of HTTPS connections on non-standard ports.

url: support client certificate files over HTTPS (issue643) This extends the httpshandler with the means to utilise the auth section to provide it with a PEM encoded certificate key file and certificate chain file. This works also with sites that both require client certificate authentication and basic or digest password authentication, although the latter situation may require the user to enter the PEM password multiple times.

acl: support for getting authenticated user from web server (issue298) Previously, the acl extension just read the current system user, which is fine for direct file system access and SSH, but will not work for HTTP(S) as that would return the web server process user identity rather than the authenticated user. An empty user is returned if the user is not authenticated.

hgweb: escape REMOTE_HOST when passing url for addchangegroup If DNS lookups are turned off on the web server, REMOTE_HOST may be populated with REMOTE_ADDR, which, if the remote is an IPv6 hosts will contain colons, thus interfering with the separator character. This is solved by URL quoting the REMOTE_HOST string.

tests: fix test for convert detection of p4 repos

kill trailing whitespace

graphmod/webcommands: use generic DAG walks Changes graph() to colorededges(), which operates on the new generic DAG walks and adds color and edge information needed by the web graph. This is in preparation of adding DAG walk filters, like the linear run collapser in the next patch. The idea is to have a bunch of changelog walkers that return basic data. Then we can filter this data. Finally we add edge and formatting info suitable for the output media we want to target (glog, hgweb).

graphmod: rename a bunch of vars in graph()

graphmod/graphlog: make dag walks carry data as type, payload

graphlog: rename grapher to asciiedges

graphlog: move and rename graphabledag to asciiformat

graphmod/graphlog: extract nodelistwalk

graphmod/graphlog: move log walks to graphmod

graphmod: code cleanup and doc fix

merge: rename -S/--show option to -P/--preview

mq: unify code for qdel -r and qfin

mq: warn about finalizing patches without cset message

filemerge: add internal:dump This create foo.{local,other,base} files for people to manually merge files while littering their working directory.

filemerge: add internal:prompt target

convert: Make P4 conversion cope with keywords, binary files and symbolic links. Convert now handles errors from p4 during conversion more gracefully. If keyword expansion is enabled in a P4 file then keywords will be unexpanded in hg. Added testcase for p4 filetypes and keyword (un)expansion. This testcase ignores UTF and Apple files to avoid binary data. Edited by pmezard: fixed collation issue on OSX

i18n-zh_TW: Traditional Chinese translation

patchbomb: update test output to match 2aff285b902f

patchbomb: do not assume the presence of angle brackets around msg-id RFC 5322 states: "Semantically, the angle bracket characters are not part of the msg-id; the msg-id is what is contained between the two angle bracket characters." Hence it should be correct to pass a message Id with no angle brackets to --in-reply-to. Adding them if missing.

keyword: concise help title

interhg: upgrade comments to online help and improve them Some inspiration taken from the wiki page of the extension.

churn: improve description Thanks to Martin Geisler and timeless for the suggested improvements.

doc: fix regexp for determining the man page section Preceding a .* pattern with an other dot serves little purpose, better anchor the regexp to the start of the file name.

Fix test-convert-cvsnt-mergepoints so it works reliably. Specifically, always run 'cvs commit' with -f option to force commit; add one strategic sleep which seems to be necessary for post-merge clobber-and-commit (-f doesn't force a commit there?).

test-convert-cvsnt-mergepoints: make it work on OS X. - don't create file 'cvs' where directory 'CVS' already exists

test-convert-cvsnt-mergepoints: ignore differences between CVS 1.11 and 1.12. - factor out cvsci function (similar to other test-convert-cvs* scripts) - add filterpath function (also similar to other scripts) - generally munge the output of CVS - add lots of output to make it easier to follow when things go wrong This doesn't make the test pass reliably under CVS 1.11; it just makes it behave the same as under CVS 1.12, i.e. sometimes it passes and sometimes it fails. Failure is more frequent with faster hardware.

Rename CVSNT "mergepoints" test and make it executable. - rename test-convert-cvs-builtincvsps-cvsnt-mergepoints (and related files) to test-convert-cvsnt-mergepoints - this ensures that the test will be run, but does NOT make it pass: in particularly, it fails regularly for me due to the inconsistent behaviour of CVS itself - expect "Branchpoints:" in debugcvsps output

Fixed patch.eol bug that truncated all patched lines to one character Also updated the import-eol test to test with lines longer than one character, and also empty lines.

subrepo: add a test

subrepo: basic push support

subrepo: add update/merge logic

commit: recurse into subrepositories

subrepo: introduce basic state parsing

Make mq, record and transplant honor patch.eol

Add patch.eol to ignore EOLs when patching (issue1019) The intent is to fix many issues involving patching when win32ext is enabled. With win32ext, the working directory and repository files EOLs are not the same which means that patches made on a non-win32ext host do not apply cleanly because of EOLs discrepancies. A theorically correct approach would be transform either the patched file or the patch content with the encoding/decoding filters used by win32ext. This solution is tricky to implement and invasive, instead we prefer to address the win32ext case, by offering a way to ignore input EOLs when patching and rewriting them when saving the patched result.

gpg: add test

gpg: unbreak 02a12835b17e. We need a test.

share: allow dest to default to the basename of source

Merge with crew

bisect: improve --command output - Display tested revisions without --verbose - Display revision number

dirstate: fix typo introduced by 3507f6c7715c

test-bisect: test --command option

bisect: fix traceback when command executable is not found

share: add experimental share extension

add helper function to create shared repos

repo: add internal support for sharing store directories set .hg/sharedpath to point to the .hg to share with

remoteui: properly create dst with copy()

repo: set up ui and extensions earlier

localrepo: remove 'closed' argument to heads(...) function - repository heads are not associated with the closed attribute, so remove it making the code in line with the concept. - Fix functions that were calling heads with the parameter. - Adjust webcommands.branches to include the concept of inactive as well as open and closed branches - Fix code and docstrings in commands to make the correct use of closed branches & branch heads clearer - Improve grammar of 'hg heads' help text (2nd submission) this does not alter the cli for hg branches, that work is still to be done

mq: eliminate warning on qpush with empty series Warning was "DeprecationWarning: use lock.release instead of del lock"

inotify: repowatcher: don't use a watches attribute to count watches The encapsulated watcher alread has a __len__ method for this purpose. Also, repowatcher.watches was never decremented on watch deletions.

inotify: put the "while True: poll()" loop in pollable class

inotify: refactor (un)register methods into pollable object repowatcher.master becomes unnecessary

inotify.server: the decorator eventaction() shouldn't be a method of repowatcher

inotify: add log config option redirect inotify server output to a file

cmdutil: service: logfile option to redirect stdout & stderr in a file

inotify: raise QueryFailed when the server crash When the server crashes, it does not write back on the socket. The message which is then read from the socket is '', which raises a TypeError. Catching TypeError to raise QueryFailed instead.

inotify: server: move split() out of server split() has nothing to do with the server logic, it does not need to be in the class. Move it on top, next to join() which does the opposite.

inotify: remove unused variables

atomictempfile: fix exception in __del__ if mktempcopy fails (self._fp is None) Make what is going on more obvious by explicitely getting the 'closed' attribute from _fp, instead of from the gettatr proxy.

Merge with crew-stable

bzr convert: restore paths to source encoding. Closes issue1692.

doc: wrap man pages after fixing quoting

hgrc.5: fix quoting of literal strings The quotes would go wrong in many places due to differences between asciidoc version 8.2.7 used by Benoit and 8.4.5 used by me. Between those versions asciidoc stopped interpreting the content of `quoted strings`, and so `*` would start bold text in the old version, but do nothing in the new version. To complicate things further, `\*` would escape the bold tag in the old version, but in the new version the backslash was inserted literally into the output (because the backtick quotes it). I've now replaced backticks with non-quoting plusses and escaped backslashes as appropriate.

hgignore.5: remove extra quotes The so-called "unconstrained quotes" didn't really work, so I reverted them to normal quotes. Tested with asciidoc version 8.2.7 and 8.4.5.

Improve English for help text of many core hg commands. co-author: Greg Ward <greg-hg@gerg.ca>

use new style classes

doc: correctly escape *

doc: correctly escape *

hg.1: highlight references to commands and man pages

hg.1: simplify synopsis Now that arguments can be mixed with options we can simplify the synopsis considerably. Also, highlighting the command name in bold (instead of italics) seem to be the standard convention.

hgrc.5: spell check

man pages: add meta data This removes the fixme's that were otherwise inserted.

man pages: updated copyright years

hgrc.5: use NOTE admonition paragraph

hgrc.5: reformatted to avoid big chunks of monospaced text The man page used to have lines longer than 80 characters, even though all lines in the hgrc.5.txt file were wrapped nicely. The problem turned out to be that the indented paragraphs started literal blocks instead of normal paragraphs. The literal blocks were of course not wrapped when displayed by man. In short, the asciidoc rules require lists to be formatted like this: foo:: Some description of foo. + Another paragraph in the description of foo. It *must* start flush left and the plus is necessary to indicate that this is a list item continuation. Lists with nested lists can be formatted correctly using something called "open blocks". These blocks are used to group the list items and are marked by a line above and below with two dashes. See the asciidoc user guide for the gory details...

hgrc.5: mark filename patterns as monospaced text

hgrc.5: single quotes means italic in asciidoc Use double quotes instead and mark the * as monospaced text.

man pages: mark filenames and env vars as fixed text

test-convert-svn-*: no longer need the url building code

convert: default to file protocol when no :// found for svn repo url Edited by pmezard: add path separator normalization

keyword: improve English

bookmarks: improve English

Generally replace "file name" with "filename" in help and comments.

Spell Mercurial as a proper noun

win32text: drop disabling portion of test disabling extension leaves dirstate confused about whether affected files are clean or not, not much point testing it.

i18n-de: Synchronised with hg.pot translated by Fabian Kreutz <fabian.kreutz@qvantel.com> Tobias Bell <tobias.bell@gmail.com>

i18n-pt_BR: synchronized and updated - synchronized with hg 6019e6517f95 - translated remaining messages - many spelling and formatting fixes

convert: better support for CVS branchpoints (issue1447) This records the branches starting at individual CVS file revisions, using the symbolic names map rather than just the branches information. This information is used to generate Mercurial changesets. Despite the changes, the CVS conversion still suffers heavily from cvsps' deficiencies in generating a correct representation of the CVS repository history.

Merge with stable

Merge with crew