match: allow passing a context object to match core

fileset: drop matchfn This is now built into contexts

scmutil: match no longer accepts repo objects

scmutil: switch match users to supplying contexts The most appropriate context is not always clearly defined. The obvious cases: For working directory commands, we use None For commands (eg annotate) with single revs, we use that revision The less obvious cases: For commands (eg status, diff) with a pair of revs, we use the second revision For commands that take a range (like log), we use None

scmutil: match now accepts a context or a repo

context: add a match builder method This is groundwork for matching against filesets in contexts

help/hgignore: refer to the builtin help instead of external URLs

sslutil: make messages for Python without certificate handling more helpful We now explain why there is no certificate to verify and do not give hints about cacerts when they can't be used anyway.

sslutil: fall back to commonName when no dNSName in subjectAltName (issue2798) Any entries in subjectAltName would prevent fallback to using commonName, but RFC 2818 says: If a subjectAltName extension of type dNSName is present, that MUST be used as the identity. Otherwise, the (most specific) Common Name field in the Subject field of the certificate MUST be used. We now only consider dNSNames in subjectAltName. (dNSName is known as 'DNS' in OpenSSL/Python.)

merge with i18n

svn subrepos: work around checkout obstructions (issue2752) We do this by ensuring the working copy is clean and then blowing away the working copy and replacing it with one from the desired path. We could probably use 'svn switch' to do this more efficiently, but there's some subtle logic required to get that right and this is more likely to work reliably.

update: check wc.dirty() before setting overwrite=True merge.update() was missing a few dirtiness checks from workingcontext, including subrepo cleanliness checks. Using wc.dirty() instead of one-off checks for various forms of dirtiness will be significantly safer.

tags: don't allow environment errors to be raised from _writetagscache See https://bitbucket.org/tortoisehg/thg/issue/719

help/config: replace docutils markup

test-i18n, i18n-pt_BR: update test message This changes both a test and a translation, so I'm sending a patch; please let me know if I should push this directly to i18n instead.

config: undo change of empty line definition We don't allow spaces in front of comment markers

patch: make filestore store data in memory and fallback to fs

i18n: merge in latest Romanian translations

i18n-ro: synchronized with 3c7907dc95ca

i18n-ro: outstanding changes

help/config: quote config section names consistently

help/config: fix small typo

help/config: do not refer to config files as hgrc files

help/config: fix 'Mercurial' casing