bookmarks: move update into core

bookmarks: move read methods to core

bookmarks: move basic io to core

extensions: add an ignore list for old extensions

run-tests: only call WIFEXITED on systems it exists not on Windows or in jython

run-tests: loadable as module

hgignore: ignore more bytecode ignore optimized bytecode and jython bytecode

doc: Capitalize the "options" header of mercurial commands

doc: Add back quotes around filenames Filenames starting with a dot (.hg and .hgignore) confuse man when creating the ps documentation with "man -t hg >hg.ps" if they are not enclosed in back quotes.

merge with stable

opener: use posixfile to hold file open when calling nlinks() Mercurial's posixfile is less intrusive on Windows than Python's open

remove pointless os.path.join calls when opening files in .hg/cache Windows deals just fine with '/' in paths and Mercurial on Windows already does file accesses elsewhere with mixed \ and / in file paths anyway. This patch also makes the static-http repo case use proper URLs of the form http://example.com/repo/.hg/cache/branchheads http://example.com/repo/.hg/cache/tags instead of the entirely pointless http://example.com/repo/.hg/cache%5Cbranchheads http://example.com/repo/.hg/cache%5tags (as introduced by 5ccdca7df211)

backout: make help more explicit about what backout does The help for backout explains: The backout command merges the reverse effect of the reverted changeset into the working directory. Unfortunately, that does not make it obvious to a newcomer what the backout command does. Since it performs a 3-way merge, what is the common ancestor? Will the result be automatically committed? What is this reverted changeset --- is it the rev passed with -r on the command line or its inverse? So try to clarify the description, avoiding jargon and being explicit about what happens from the user's perspective. Thanks to Gilles Moris, Steve Borho, Kevin Bullock, and timeless for help.

subrepo: fix pruning of subrepo filenames in dirstate (issue2619)

merge with self

merge with stable

Added signature for changeset 2b2155623ee2

Added tag 1.7.5 for changeset 2b2155623ee2

merge with crew

Merge with stable

subrepo: fix update -C with svn subrepos when cwd != repo.root

test-subrepo-git.t: make compatible with old git

win32mbcs: Fix typo in documentation extention -> extension

merge with stable

url: add --insecure option to bypass verification of ssl certificates If --insecure specified, it behaves in the same way as no web.cacerts configured. Also shows hint for --insecure option when _verifycert() failed. But currently the hint isn't displayed on SSLError, because it needs a certain level of changes.

mq: factor out push conditions checks Some extensions (e.g. hgsubversion) completely override push command. Because extensions load order is unspecified, if hgsubversion loads before mq, mq checks about not pushing applied patches will be bypassed. Short of finding a way to fix load order, extracting the checking logic will allow hgsubversion-like extensions to run the check themselves.

test-subrepo-mq-svn.t: correct comment This fixes the description of a helper function in the test.

subrepo: clarify comments in dirty() methods Just a little change to bring the comments in the dirty() methods of the various subrepo classes into a uniform structure. This clarifies the meaning of the states checked.

subrepo: make update -C clean the working directory for git subrepos This makes 'hg update --clean' behave the same way for all three kinds of subrepositories [hg, svn, git]. Before git subrepos did not take the clean parameter into account, but just updated to the given revision and merged uncommitted changes into that.

merge with stable

subrepo: make update -C clean the working directory for svn subrepos This makes 'hg update --clean' behave the same way for both kinds of subrepositories. Before Subversion subrepos did not take the clean parameter into account, but just updated to the given revision and merged uncommitted changes into that.

Added signature for changeset a6c855c32ea0

Added tag 1.7.4 for changeset a6c855c32ea0

i18n-pt_BR: messages from crew a939f08fae9c

merge with i18n stable

i18n-pt_BR: messages from crew 8dc488dfcdb4, some small fixes

util: delay loading of textwrap

merge with stable

url: 'ssh known host'-like checking of fingerprints of HTTPS certificates Known fingerprints of HTTPS servers can now be configured in the hostfingerprints section. That makes it possible to verify the identify of web servers without configuring and trusting the CA chain. Limitations: * Portnumbers are ignored, just like with ordinary certificates. * Host name matching is case sensitive.

merge with stable

merge with i18n

i18n-merge stable heads

i18n-de: translated some rebase strings.

i18n-de: translated missing strings for progress extension.

i18n-pt_BR: synchronized with 75d0c38a0bca

bookmarks: respect rollbacks dryrun parameter

bookmarks: always write undo file Always write the undo file. Otherwise, rollback will not work for the initial bookmark as undo.bookmarks doesn't exists. In this case undo.bookmarks needs already be empty.

opener: force copy on 'a'ppend if nlinks() returns 0 (issue1922) If pywin32 is not installed, 'os.lstat(pathname).st_nlink' is used for nlinks(), which is always zero for all files on Windows. To make sure we break up hardlinks if pywin32 is missing, we force nlink = 2 if nlinks() returns < 1. (this completely fixes issue1922)

help: ssh urls don't allow passwords

commit: use the term SCM instead of RCS for consistency. see also fc4a3931e608

backout of 613b8bd2284e Matt and a majority of crew did not like this approach.

check-code: do not complain about 'ls x | foo -v' Such a line was introduced in test-subrepo-git.t in 5dda6c708138, which made check-code confused.

subrepo: separate out mq+svn subrepo tests Having the mq+subrepo+svn tests in a separate file lets them be skipped without skipping the other mq+subrepo tests.

keyword: move repo.__class__ assignment out of monkeypatch context A cosmetic change to improve readability.

keyword: inform user about current keywordset in kwdemo The kwdemo --default output now looks roughly like this: configuration using default cvs keywordset [extensions] keyword = [keyword] demo.txt = [keywordset] * section added with this change svn = False [keywordmaps] ...

specify C indention style using Emacs file local variables

Ignore pax_global_header that some tar versions write as a file.

record: do not include files into changes count This turns the prompt sequence from something like: $ examine changes to foo? $ record change 1/4 to foo? $ record change 2/4 to foo? $ examine changes to bar? $ record change 4/4 to bar? into: $ examine changes to foo? $ record change 1/3 to foo? $ record change 2/3 to foo? $ examine change to bar? $ record change 3/3 to bar?

record: simplify header methods with util.any

record: refactor the prompt loop The previous loop was iterating over a mixed header/hunk stream. It may have been more generic in the sense every item in the stream could trigger a prompt but it required more work to skip items properly. It can be rewritten in a more intuitive way by looping on files then looping on hunks.

test-record: test peculiar changes numbering

record: turn prompt() into a pure function

record: turn consumefile() into a pure function

hghave: remove unused hotshot check

Merge with stable

subrepo: compare svn subrepo state to last committed revision A subversion project revisions are a subset of the repository revisions, you can ask subversion to update a working directory from one revision to another without changing anything. Unfortunately, Mercurial will think the subrepository has changed and will commit it again. To avoid useless commits, we compare the subrepository state to its actual "parent" revision. To ensure ascending compatibility with existing subrepositories which might reference fake revisions, we also keep comparing with the subrepo working directory revision. NOTE: not sure if this should go in stable or not.

merge with stable

win32: win32console.GetStdHandle() can return None When the Mercurial Python libraries are used within a Windows application with no console, there is no stderr file handle.

revlog: remove stray test in rev()

merge with main

opener: use util.unlink (issue2524)

lock: use util.unlink (issue2537)

reintroduces util.unlink, for POSIX and Windows. windows: factor it out of rename posix: add alias 'unlink' for os.unlink Note that this new unlink function now has different semantics than the unlink() we had before changeset 6bf39d88c857 ("rename util.unlink to unlinkpath").

opener: check exception for ENOENT

windows.rename: check OSError for EEXIST For example, if src has been opened with Python's open(), os.rename will raise EACCES. Continuing in that case is pointless.

perf: restore lazyindex hack This hack (and the module it lives in) exist so that performance can be compared across different hg versions.

revlog: pass rev to _checkhash

revlog: incrementally build node cache with linear searches This avoids needing to prime the cache for operations like verify which visit most or all of the index.

bundlerepo: use less intrusive util.posixfile to open bundle

osutil: treat open modes 'w' and 'a' as 'w+' and 'a+' in posixfile to work around http://support.microsoft.com/kb/899149. Also, Microsoft's documentation of the CreateFile Windows API says (quote): When an application creates a file across a network, it is better to use GENERIC_READ | GENERIC_WRITE for dwDesiredAccess than to use GENERIC_WRITE alone. The resulting code is faster, because the redirector can use the cache manager and send fewer SMBs with more data. This combination also avoids an issue where writing to a file across a network can occasionally return ERROR_ACCESS_DENIED.

move tags.cache and branchheads.cache to a collected cache folder .hg/cache/ The generation of cache files like tags.cache and branchheads.cache is not an actual reflection of things changing in the whole of the .hg directory (like eg a commit or a rebase or something) but instead these cache files are just part of bookkeeping. As such its convienant to allow various clients to ignore file events to do with these cache files which would otherwise cause a double refresh. Eg one refresh might occur after a commit, but the act of refreshing after the commit would cause Mercurial to generate a new branchheads.cache which would then cause a second refresh, for clients. However if these cache files are moved into a directory like eg .hg/cache/ then GUI clients on OSX (and possibly other platforms) can happily ignore file events in this cache directory.

addchangegroup: document the current locking semantics

keyword: update documentation for kwshrink * remove obsolete reference to potential problems with merge and import * emphasize that running kwshrink before configuration changes which affect active/expanded keywords is mandatory

tests: remove duplication of the CGI environment variables

revlog: explicit test and explicit variable names

revlog: if the nodemap is set, use the fast version of revlog.rev()

revlog/parseindex: construct the nodemap if it is empty

revlog: always add the magic nullid/nullrev entry in parseindex

revlog/parseindex: no need to pass the file around

parsers.c: fix comment

perf: there is no lazy index anymore

pure: update index parsing

perf: fix ordering of invalidate in perfindex

revlog: do revlog node->rev mapping by scanning Now that the nodemap is lazily created, we use linear scanning back from tip for typical node to rev mapping. Given that nodemap creation is O(n log n) and revisions searched for are usually very close to tip, this is often a significant performance win for a small number of searches. When we do end up building a nodemap for bulk lookups, the scanning function is replaced with a hash lookup.

revlog: introduce a cache for partial lookups Partial lookups are always O(n), and often we look up the same one multiple times.

tags: avoid a pointless usage of revlog.nodemap