upstream/mercurial-mirror Files · mercurial/help/urls.txt

perf: import newer modules separately for earlier Mercurial...

perf: import newer modules separately for earlier Mercurial demandimport of early Mercurial loads an imported module immediately, if a module is imported absolutely by "from a import b" style. Recent perf.py satisfies this condition, because it does: - have "from __future__ import absolute_import" line - use "from a import b" style for modules in "mercurial" package Before this patch, importing modules below prevents perf.py from being loaded by earlier Mercurial, because these aren't available in such Mercurial, even though there are some code paths for Mercurial earlier than 1.9. - branchmap 2.5 (or bcee63733aad) - repoview 2.5 (or 3a6ddacb7198) - obsolete 2.3 (or ad0d6c2b3279) - scmutil 1.9 (or 8b252e826c68) For example, setting "_prereadsize" attribute in perfindex() and perfnodelookup() is effective only with Mercurial earlier than 1.8 (or 61c9bc3da402). After this patch, "mercurial.error" is the only blocker in "from mercurial import" statement for loading perf.py with Mercurial earlier than 1.2. This patch ignores it, because just importing it separately isn't enough.

Mike Williams - - Load All Authors

File last commit:

r19197:01d68fb0 stable


                r29567:7e2b3894

default

Download file

             urls.txt
        
                    66 lines
            
             | 2.3 KiB
            
                | text/plain
            
             |
                TextLexer

/ mercurial / help / urls.txt

History | Source | Raw |Copy content |Copy permalink

Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	Valid URLs are of the form::

		local/filesystem/path[#revision]
Mads Kiilerich help: Backed out changeset e99facd2cd2a, description of file urls...	r15533	file://local/filesystem/path[#revision]
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	http://[user[:pass]@]host[:port]/[path][#revision]
		https://[user[:pass]@]host[:port]/[path][#revision]
Matt Mackall help: ssh urls don't allow passwords	r13304	ssh://[user@]host[:port]/[path][#revision]
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		Paths in the local filesystem can either point to Mercurial
Mike Williams help: stop documentation markup appearing in generated help...	r19197	repositories or to bundle files (as created by :hg:`bundle` or
		:hg:`incoming --bundle`). See also :hg:`help paths`.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		An optional identifier after # indicates a particular branch, tag, or
Martin Geisler Use hg role in help strings	r10973	changeset to use from the remote repository. See also :hg:`help
		revisions`.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		Some features, such as pushing to http:// and https:// URLs are only
		possible if the feature is explicitly enabled on the remote Mercurial
		server.

Mads Kiilerich doc: clarify that https cert verification requires web.cacerts	r12593	Note that the security of HTTPS URLs depends on proper configuration of
		web.cacerts.

Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999	Some notes about using SSH with Mercurial:

		- SSH requires an accessible shell account on the destination machine
		and a copy of hg in the remote path or specified with as remotecmd.
		- path is relative to the remote user's home directory by default. Use
		an extra slash at the start of a path to specify an absolute path::

		ssh://example.com//tmp/repository

		- Mercurial doesn't use its own compression via SSH; the right thing
		to do is to configure it in your ~/.ssh/config, e.g.::

		Host *.mylocalnetwork.example.com
		Compression no
		Host *
		Compression yes

Brodie Rao help: refer to user configuration file more consistently...	r12083	Alternatively specify "ssh -C" as your ssh command in your
		configuration file or with the --ssh command line option.
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
Brodie Rao help: refer to user configuration file more consistently...	r12083	These URLs can all be stored in your configuration file with path
		aliases under the [paths] section like so::
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		[paths]
		alias1 = URL1
		alias2 = URL2
		...

		You can then use the alias for any command that uses a URL (for
Martin Geisler Use hg role in help strings	r10973	example :hg:`pull alias1` will be treated as :hg:`pull URL1`).
Dan Villiom Podlaski Christiansen setup: install translation files as package data...	r9999
		Two path aliases are special because they are used as defaults when
		you do not provide the URL to a command:

		default:
		When you create a repository with hg clone, the clone command saves
		the location of the source repository as the new repository's
		'default' path. This is then used when you omit path from push- and
		pull-like commands (including incoming and outgoing).

		default-push:
		The push command will look for a path named 'default-push', and
		prefer it over 'default' if both are defined.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages