discovery: avoid discovery when local graph is a subset of remote Immediately sends local's heads to the server to check whether the server knows them all. If it does, we can call getbundle immediately. Interesting test output changes are: - added 1 changesets with 0 changes to 1 files (+1 heads) + added 1 changesets with 0 changes to 0 files (+1 heads) -> The new getbundle() actually fixes a bug vs. changegroupsubset() in that it no longer returns unnecessary files when file revs are reused. warning: repository is unrelated + requesting all changes -> The new use of common instead of bases correctly indicates that an unrelated pull gets all changes from the server.

wireproto: add getbundle() function getbundle(common, heads) -> bundle Returns the changegroup for all ancestors of heads which are not ancestors of common. For both sets, the heads are included in the set. Intended to eventually supercede changegroupsubset and changegroup. Uses heads of common region to exclude unwanted changesets instead of bases of desired region, which is more useful and easier to implement. Designed to be extensible with new optional arguments (which will have to be guarded by corresponding capabilities).

merge with stable

i18n-pt_BR: synchronized with 6783f47d90dd

merge with i18n

i18n-it: synchronized with adf3c4401c5d

osutil: fix up check-code issues

dirstate: flush _lastnormal when we see newer filesystem times

util: add Mac-specific check whether we're in a GUI session (issue2553) The previous test assumed that 'os.name' was "mac" on Mac OS X. This is not the case; 'mac' was classic Mac OS, whereas Mac OS X has 'os.name' be 'posix'. Please note that this change will break Mercurial on hypothetical non-Mac OS X deployments of Darwin. Credit to Brodie Rao for thinking of CGSessionCopyCurrentDictionary() and Kevin Bullock for testing.

rebase: allow for rebasing descendants onto ancestors on different named branches So far we've been denying rebasing descendants onto ancestors, but there are situations in which this kind of operation makes perfect sense to me. Let's say we have made a commit (or more), that belongs to branch 'dev', on top of the named branch 'stable': ... a (stable) - b (dev) but then we realize that b should belong to branch 'stable'. In these cases a rebase means: "move these csets from named branch A to named branch B" and there isn't a valid reason to deny it. This patch basically doesn't block it, if source and destination are on different named branches. The old behaviour still applies for rebases across the same named branch. Can you think of any tricky corner cases in which this new behaviour could lead to problems? (I bet there are tons of them...) By the way, I created a brand new .t because I feel there should be more tests I can't think of at the moment.

bdiff.c: rename all variables which hold a hash value to "hash"

bdiff.c: use unsigned arithmetic for hash computation Signed integer overflow is undefined in C.

bdiff.c: cast to unsigned char when computing hash value

bdiff.c: make all local functions static

merge with stable

debugbundle: fix up long line caught by check-code

wireproto: avoid naked excepts

mq: fix typo in docstring

commands: add debugbundle command Lists ids contained in a bundle file. Useful for testing bundle-related commands.

wireproto: add known([id]) function known([Node]) -> [1/0] Returns 1/0 for each node, indicating whether it's known by the server. Needed for new discovery protocols introduced in later patches.

wireproto: fix decodelist to properly return empty list Needed by tests for next patch introducing known().

wireproto: fix handling of '*' args for HTTP and SSH

debug: add debugwireargs to test argument passing over the wire Tests argument passing locally, via HTTP, and via SSH. This is mainly preparation for the next patch.

sshserver: drop unnecessary line

merge: avoid unlinking destination of merge when case changes (issue2715)

dirstate: introduce a public case normalizing method

changegroup: minor cleanups

repair: revlog has an iterator

changegroup: fix leftover from delta read

changegroup: drop expensive redundant usage of readdelta for progress

changegroupsubset: use manifest.readfast to simplify collector

manifest: add readfast method

changegroupsubset: simplify filenode_collector

changegroupsubset: more renaming

changegroupsubset: simplify prune Ancestors of nodes linked to commonrevs can be expected to be linked to commonrevs. Walking graphs of each revlog looking for rare/nonexistent outliers is overkill.

changegroupsubset: more minor cleanups - remove more excessive comments - simplify some sorting operations - rename some variables - replace identity with a lambda

changegroupsubset: minor cleanups - move some variable declarations - drop some excessive comments - use standard variable naming

strip: simplify collectone

dirstate: avoid a race with multiple commits in the same process (issue2264, issue2516) The race happens when two commits in a row change the same file without changing its size, *if* those two commits happen in the same second in the same process while holding the same repo lock. For example: commit 1: M a M b commit 2: # same process, same second, same repo lock M b # modify b without changing its size M c This first manifested in transplant, which is the most common way to do multiple commits in the same process. But it can manifest in any script or extension that does multiple commits under the same repo lock. (Thus, the test script tests both transplant and a custom script.) The problem was that dirstate.status() failed to notice the change to b when localrepo is about to do the second commit, meaning that change gets left in the working directory. In the context of transplant, that means either a crash ("RuntimeError: nothing committed after transplant") or a silently inaccurate transplant, depending on whether any other files were modified by the second transplanted changeset. The fix is to make status() work a little harder when we have previously marked files as clean (state 'normal') in the same process. Specifically, dirstate.normal() adds files to self._lastnormal, and other state-changing methods remove them. Then dirstate.status() puts any files in self._lastnormal into state 'lookup', which will make localrepository.status() read file contents to see if it has really changed. So we pay a small performance penalty for the second (and subsequent) commits in the same process, without affecting the common case. Anything that does lots of status updates and checks in the same process could suffer a performance hit. Incidentally, there is a simpler fix: call dirstate.normallookup() on every file updated by commit() at the end of the commit. The trouble with that solution is that it imposes a performance penalty on the common case: it means the next status-dependent hg command after every "hg commit" will be a little bit slower. The patch here is more complex, but only affects performance for the uncommon case.

changegroupsubset: extranodes are no longer needed

strip: remove usage of extranodes Instead of computing the exact set of missing revlog revisions, we only compute the set of missing/broken changesets. The resulting bundle can be slightly bigger but we will be able to get rid of the ugly extranodes handling in changegroupsubset.

patch: move closefile() into patchfile.close()

patch: inline patchfile.hashlines()

patch: fix hunk newlines when parsing hunks, not in iterhunks()

i18n: register new template keywords for translation

annotate: catch nonexistent files using match.bad callback (issue1590)

merge with stable

wix: add new file templates/paper/bookmarks.tmpl This file was snuck onto the stable branch with 38c9837b1f75

merge with stable

push/outgoing: print remote target path even if there's an error (issue2561) This is a simple patch to make hg push/hg outgoing print their remote target path even if the operation fails. I'm not sure if the original behavior was by design. This patch also changes one test to reflect the changed behaviour.

subrepo: recognize scp-style paths as git URLs

convert: add svnrev, svnpath and svnuuid template keywords $ hg -R A-hg log --template '{rev} {svnuuid}{svnpath}@{svnrev}\n' 10 644ede6c-2b81-4367-9dc8-d786514f2cde/trunk@10

convert/svn: extract revsplit() in a function

transplant: add "transplanted" keyword $ hg log --template '{rev} {transplanted}\n' 7 a53251cdf717679d1907b289f991534be05c997a

merge with i18n

i18n: merge with stable

i18n-da: synchronize with e9628665b670

i18n: don't mark trivial string for translation

i18n: merge with mpm

i18n-de: correct translation for some fuzzy strings

i18n-de: synchronize with 994510694b1d

i18n-de: added translations concerning hardlinks

i18n-de: added more translations concerning rebase

i18n-de: added translations concerning rebase

i18n-de: added translations concerning email sending

i18n-de: added translations concerning patches

i18n-de: added translations concerning win32text and .hgeol

i18n-de: added translations for Perforce conversion options

i18n-de: added translations for Subversion conversion options

i18n-de: added translation for CVS conversion options

i18n-de: added translations for convert.hg.* options

i18n-de: translate some strings

revset: fix a number of highly dubious continue statements This patch definitely needs a review and would also benefit from some new testsuite entries.

graphlog: do not swallow all TypeError exceptions (fix 29c800ee54cf)

archive: use hardcoded constants when creating .zip archives Do not rely on local stat constants, which may differ.

hgweb: support multiple directories for the same path [paths] /dir = /path/1/*, /path/2/*

templates: provide granularity for future values for age filter

revset: report a parse error if a revset is not parsed completely (issue2654)

config: use util.posixfile

bundle: update current bookmark to most recent revision on current branch We check if the current bookmark is set to the first parent of the dirstate. Is this the case we move the bookmark to most recent revision on the current branch (where hg update will update you to).

localrepo: do not update bookmarks in addchangegroup We want to update the current bookmark to the most recent revision on current branch unless there is a remote bookmark that points to a different descendant. Addchangegroup is called before we can check for remote bookmarks. We don't update the bookmark in addchangegroup anymore to allow proper updating of bookmarks in pull.

rebase: add -m/--message to rebase --collapse (issue2389) When collapsing changesets with rebase, you get a chance to edit the commit message manually, but there is no way to pass this message from the command line. This patch adds a `--message` (with short form `-m`) and `--logfile` (with short form `-m`) options to the rebase command. These options suppresses the generation of the default commit message, and instead use the message provided in the option (in case of `-m`) or in the file it points to (in case of `-l`). If you use this option without the `--collapse` option, it will raise an error. Options documentation edited by Patrick Mezard <pmezard@gmail.com>

Updating hgext.extdiff to use revsets

merge with stable

relink: mark abort message for translation

relink: avoid trying to lock the same repo twice

relink: format reclaimed byte count nicely

test-relink: remove unnecessary ui.username setting

test-https: match output from 31eac42d9123

merge with stable

merge with crew

convert/svn: fix _iterfiles() output in root dir case (issue2647) When converting directory additions/replacement with project directory set to root, _iterfiles() sometimes returned paths starting with a slash making following svn calls to fail. I could not reproduce the issue with hand-crafted repositories. Report and first analysis by Clinton Chau <clinton@clearcanvas.ca>

eol: no need to accumulate files when checking all changesets Just check the files touched by the changesets.

eol: improve hook failure output Before, only the first failure was reported: abort: b.txt should not have CRLF line endings while now all of them are listed: abort: end-of-line check failed: d.txt in a7040e68714f should not have CRLF line endings b.txt in fbcf9b1025f5 should not have CRLF line endings As first suggested by Antoine Pitrou <solipsis@pitrou.net>

merge with stable

bookmarks: remove API limitation in setcurrent setcurrent refuses to set a new current bookmark if the current bookmark points to the current dirstate. This restriction is not needed. A current bookmark can point to a different bookmark.

bookmarks: separate bookmarks update code from localrepo's pull. We explicitly want to update bookmarks from a remote. This will avoid duplicate calls to listkeys if we clone (which calls pull) and keep bookmark related code together.

tests: add tests for bookmarks support in hg identify

identify: list bookmarks for remote repositories

hgignore: ignore dll files generated under cygwin

pager: don't page stderr if it's being redirected (issue2541)

color: port to using ctypes (issue2687) replacing usage of pywin32, which was removed for Mercurial 1.8

hgweb: drop use of super() for Exception base class In Python 2.4, Exception is an old-style class and doesn't work with super.

diff: make diff -c aware of revision sets

color: wrap lines in docstring

merge with stable

setup: fix mac build broken by e42d18538e1d Sometimes xcodebuild prints warnings to stderr, but runcmd() assumes anything printed to stderr implies failure. Since runcmd() was originally only intended to run hg, this was fine until it was pressed into service for running xcodebuild. Thus: split runcmd() into two parts: runcmd(), which does the minimal amount of work to run a subprocess, and runhg(), which calls runcmd().

color: don't mention internal function in docstring The render_text function actually never existed, the docstring probably meant the render_effects function instead.

keyword: offer additional datefilters when the extension is enabled Before the additional datefilters (utcdate, svnisodate, svnutcdate) were used when kwtemplater was initialized. Now they always be used once the extension is enabled.

keyword: docstrings for additional date filters

mq: do not let qrefresh write bad patch

graphlog: give meaningful error if more than one file is given

merge with stable

test-https: update to match output from 3f6a4579f803

tests: respect new hg clone listkey queries in http-proxy test

bookmarks: discard current bookmark if absent from the bookmarks (issue2692) After a rollback, the current bookmark might be absent from the bookmarks file. In that case we discard it instead of displaying a traceback during commit.

fix test-highlight after bookmark support change for hgweb

merge with stable

eol: do not abort when win32text is found, only warn The win32text extension does not break eol or vice-versa, so it is not a fatal error to have both of them enabled. It's just folly. So spewing warnings in this condition is preferrable to aborting. When both extensions are enabled, the user now sees: % hg st the eol extension is incompatible with the win32text extension win32text is deprecated: http://mercurial.selenic.com/wiki/Win32TextExtension M hgext/eol.py

merge with stable

tests: fix failures introduced in 7359cb753a54

tests: fix permission issue trying to remove test directory

bookmarks: fix update of the current bookmark during rename We need to get rid of the previous bookmark after changing current bookmark.

setup: remove unnecessary code for win32com (pywin32)

test-highlight: fix test output (introduced by 2151703e7f84)

eol: rename hook into checkheadshook, add checkallhook (issue2665) "hook" is still an alias for "checkheadshook".

eol: make the hook check all new heads, not only tip (issue2666) Report and test by Antoine Pitrou <solipsis@pitrou.net>

eol: the hook no longer requires the extension to be loaded Reading rules in the hook means we no longer need ui to be filled and do not need reposetup() to be run anymore.

eol: extract parsing error handling in parseeol()

eol: separate .hgeol parsing from merge in ui This will help refactoring the hook.

eol: remove unused argument in readhgeol()

eol: explain why reading .hgeol from the working dir is special

templates: widen the graph canvas (issue2683)

rebase: don't use util.Abort for an internal error

help: limit documentation width to at most 80 characters Reading long lines is suboptimal no matter how wide the terminal is.

merge with stable

transplant: avoid the word "rebase" when we mean "transplant"

transplant: explain that changesets are copied, not moved

hg: add support for cloning bookmarks

httprepo: use caps instead of between for compat check We usually query the capabilities at some point anyway so this way the first roundtrip actually does useful work.

revset: add a revset command to get bisect state.

bisect: new command to extend the bisect range (issue2690) When bisect ends in a merge point, and one of the parent wasn't checked, this usually means the culprit is in a branch that wasn't scanned. For this case we provide a new command which extends the range of the bisect search to the common ancestor of the parents of the merge.

hgweb: pmezard thinks one default is enough

don't depend on features of Exception as much BaseException.message has been deprecated, so we try to not rely on it.

deal with empty Content-Length headers

hgweb: add separate page with bookmarks listing

hgweb: add display of bookmarks for changelog and changeset

merge with stable

setup.py: use StrictVersion instead of manual comparison

help: extract items doc generation function

templates: document missing keywords or filters Keywords keywords are not documented yet but are turned into function definitions to avoid lambda docstring weirdness.

templatefilters: move doc from templates.txt to docstrings

templatefilters: wrap all filters in dedicated functions This will highly simplify the docstring integration. I measured "hg log --style=changelog" duration on mercurial itself and could not detect any difference.

templatefilters: prefix helper functions

templatefilters: sort function definitions

templatefilters: match filter keys and function names

templatefilters: sort filters table

templates: generate keyword help dynamically

test-help: test a sample of 'templates' topic help

fix compiling of extensions for OS X and XCode 4.0

test-subrepo-paths: fix typo

eol: use dirstate methods to clear dirstate This fixes a race that was observed when status was called before and after clearing the dirstate.

tests: fix permission issue trying to remove test directory

transplant: added 'HGREVISION' variable to the environment passed to the 'filter' command Sometimes it is necessary to know the original revision ID in order to correctly rewrite the patch or commit message when transplanting. This patch follows the pattern set by the existing 'HGUSER' environment variable, and adds a test that covers both HGUSER and HGREVISION.

test-subrepo-paths: test cummulative remapping

merge with stable

ui: yield unchanged values in walkconfig Ever since walkconfig was introduced back in 25e7ea0f2cff, the values yielded has been mutated by replacing "\n" with "\\n". This makes walkconfig less useful than it could and there is no other way to iterate over all config sections. The third-party reposettings extension used ui.walkconfig but did not take the replacement into account -- this change will actually fix a bug in the extension when a value contains a newline.

Added signature for changeset aa1f3be38ab1

Added tag 1.8.1 for changeset aa1f3be38ab1

i18n-pt_BR: synchronized with 66d65bccbf06

tests: use $TESTTMP more and use (glob) less This locks down the test output a little more.

hgweb_mod: respond right away if the client specified 100-continue support Clients that send 100-continue should make sure they really support continue intelligently. In a later patch we'll introduce a capability so new clients don't pay a performance penalty talking to old servers.

hgweb: add support for 100-continue as recommended by PEP 333.

subrepo: show the source that git pulls

commands.update() now works properly with a revision of 0 Without this change commands.update() treats an integer 0 as if no revision was passed and updates to the branch head. This fix allows an integer 0 to be detected as a revision number so the working directory is correctly changed to revision 0 rather than the branch head.

merge with stable

mergetools: add alternate registry keys for 32bit apps on 64bit O/S Not all applications needed the workarounds, so I did not add alternate keys for every Windows merge application.

filemerge: introduce a 'regkeyalt' merge tool variable This allows us to provide alternate search keys for 64bit operating systems that may have 32bit merge tools installed. Presumably it may find other uses.

merge with stable

wix: drop bin/ folder from MSI installers (issue 2673) Also fixes issue 2658.

zsh completion: remove computed default values from help texts The default encoding and encoding mode are computed at runtime and can vary from system to system. The two remaining default values in the completion help texts (number of directories to strip on import and default bundle name) are fixed in the source code.

merge: remove last traces of fastforward merging bbc97d419b16 introduced fast-forward branch merging. 66ed92ed115a partly removed it again. The fastforward variable would always be false if branchmerge was false, so the fastforward variable makes no difference and we can remove it completely.

merge with stable

subrepo: backout 67fbe566eff1, --force requires svn >= 1.5

merge with stable

merge with i18n

i18n-de: improve translation for "unmerged branches" This translation issue was pointed out by Georg Brandl.

httprepo: order URL query string fields for readability - cmd is always first, since the other fields are arguments to that command. - The other fields are in alphabetical order, rather than random order. example "hg serve" output BEFORE 127.0.0.1 - - [26/Feb/2011 14:20:07] "GET /?bases=fa5962be1d87fe9a57244a14033550e192e57521+1a38f137b190482eaf0986594cd6e6b486c76fec&cmd=changegroupsubset&heads=1a38f137b190482eaf0986594cd6e6b486c76fec+fa5962be1d87fe9a57244a14033550e192e57521 HTTP/1.1" 200 - 127.0.0.1 - - [26/Feb/2011 14:00:50] "GET /?pairs=0000000000000000000000000000000000000000-0000000000000000000000000000000000000000&cmd=between HTTP/1.1" 200 - 127.0.0.1 - - [26/Feb/2011 14:17:28] "GET /?nodes=1a38f137b190482eaf0986594cd6e6b486c76fec+fa5962be1d87fe9a57244a14033550e192e57521&cmd=branches HTTP/1.1" 200 - AFTER 127.0.0.1 - - [26/Feb/2011 14:21:28] "GET /?cmd=changegroupsubset&bases=fa5962be1d87fe9a57244a14033550e192e57521+1a38f137b190482eaf0986594cd6e6b486c76fec&heads=1a38f137b190482eaf0986594cd6e6b486c76fec+fa5962be1d87fe9a57244a14033550e192e57521 HTTP/1.1" 200 - 127.0.0.1 - - [26/Feb/2011 13:48:13] "GET /?cmd=between&pairs=0000000000000000000000000000000000000000-0000000000000000000000000000000000000000 HTTP/1.1" 200 - 127.0.0.1 - - [26/Feb/2011 14:19:17] "GET /?cmd=branches&nodes=1a38f137b190482eaf0986594cd6e6b486c76fec+fa5962be1d87fe9a57244a14033550e192e57521 HTTP/1.1" 200 -

ancestor: improve description

subrepo: don't crash when git repo is missing

ancestor: rewrite to deal with crossed linkrevs (issue2682) This version is about 10% slower, possibly because it visits some revisions in a different topological order than what's in the revlog.

hgcia: accept "queued." xmlrpc return as success

merge: back out single-parent fast-forward merge This backs out changeset: 13158:9e7e24052745 user: Mads Kiilerich <mads@kiilerich.com> date: Tue Dec 07 03:29:21 2010 +0100 summary: merge: fast-forward merge with descendant Before named branches, the invariants were: a) "merges" always have two parents b) p1 is not linearly related to p2 Adding named branches made (b) problematic, so the above patch was introduced, which fixed (b) but broke (a). After discussion, we decided that the invariants should be: a) "merges" always have two parents b) p1 is not linearly related to p2 OR p1 and p2 are on different branches

merge: drop resolve state for mergers with identical contents (issue2680)

merge with stable

hgweb: fix filelog rss links generation

hgweb: use tip in gitweb/monoblue filelog rss links (issue2677)

merge with stable

cacert: improve error report when web.cacert file does not exist

tests: improve hghave error reporting for missing Py OpenSSL

Merge with stable

Improve unresolved merge conflicts warning (issue2681) Suggested by Antoine Pitrou <pitrou@free.fr>

tests: convert test-serve to new format

run-tests: handle mixed comment lines in blacklists

test-doctest: handle unix/windows path discrepancies

test-rename-merge1: make it easier to review, windows friendly - Reuse the coding style of the previous tests, both are very similar - Do not play with case changes, it does not work on Windows

merge: drop resolve state for mergers with identical contents (issue2680)

merge with stable

match: ignore "" patterns The following command would visit every changeset in repo/ rather than the last 10: hg log -l 10 repo/

statichttprepo: abort if opener mode is 'r+' or 'rb+' The old version of the check failed to catch modifying modes 'r+' and 'rb+'.

Merge with stable

subrepo: handle svn tracked/unknown directory collisions This happens more often than expected. Say you have an svn subrepository with python code. Python would have generated unknown .pyc files. Now, you rebase this setup on a revision where a directory containing python code does not exist. Subversion is first asked to remove this directory when updating, but will not because it contains untracked items. Then it will have to bring back the directory after the merge but will fail because it now collides with an untracked directory. Using --force is not very elegant but it is much simpler than rewriting our own purge command for subversion.

convert/svn: stop using svn bindings when pushing to svn

convert/svn: read trunk name once, use None for default

mq: mention qfinish in qimport help

merge with stable

bookmark: fix invalidation of localrepo._bookmarkcurrent

subrepo: show the source that git clones

check-code: catch "echo > $HGRCPATH" too Make error message consistent with the other error messages.

merge with stable

check-code: better check for overwriting $HGRCPATH Suggested by Mads Kiilerich on IRC.

test-eol-*: remove unused config settings

mq: forbid commit of merge involving mq patches

tests: don't overwrite HGRCPATH Overwriting instead of appending to the file removes the [defaults] section put into the file by run-tests.py. It also defeats the --inotify option to run-tests.py. (Nothing was broken yet, but the lack of -d "0 0" cause changeset hashes to change unexpectedly in a test case I was editing.)

merge with stable

Added signature for changeset 2616325766e3

Added tag 1.8 for changeset 2616325766e3

contrib: update tcsh_completion for Mercurial 1.8 Added the following commands: bookmarks debugignore. Fix the tcsh parse script for the current help text layout.

merge with i18n

i18n-ja: synchronized with 0a6bca3d5273

i18n-pt_BR: synchronized with 9b617c56eb65

zsh completion: complete bookmarks where they are accepted This used to work because bookmarks were pseudo-tags, but broke once bookmarks became their own first-class object.

tests: test-mq-subrepo.t Solaris 10 sh compliance Solaris 10 sh do apparently not like temporary environment variable assignment before a function call. There is no problem with commands.

bash_completion: complete bookmarks Since bookmarks moved into core and are no longer merged with the list of tags (d012d95499f7), they don't get completed in bash_completion along with other revision specifiers. This adds a new function to provide the list of bookmarks for completion, and another, _hg_labels(), to list all tags, branches, and bookmarks. It further modifies completion for all commands where '_hg_tags; _hg_branches' was used to use '_hg_labels' instead.

mq: fix qpush recursion in _findtags when status file is wrong (issue2664) test from timeless to guard against regressing this

mq: gracefully handle malformated status file This patch prevent mq to crash when .hg/patches/status contains Malformed lines (without ":"). Blank lines are ignored and other malformed lines issue a warning.

revset: fix typo when assigning weight to reverse and limit

eol: do not abort on parse error Handle parse errors in the .hgeol similarly to how parse errors in the .hgtags file are handled: by issuing a warning. This allows the user to revert the file using 'hg revert' or 'hg update -C'.

eol: fix test typos introduced in 5007ff32f356

eol: test win32text compatible encode/decode filters