The names of these files depend on the system on which Mercurial is installed. Where multiple paths are given below, settings. This file is not version- controlled, and will not get transferred during a. Options in this file override options in all other configuration files. On Unix, most of this file will be ignored if it doesn't belong to a. See the documentation for the trusted section below for more details. On Windows 9x, %HOME% is replaced by %APPDATA%. Options in these files apply. Mercurial commands executed by this user in any directory. Options in these files override per- system and per- installation options. Options in these files apply to all Mercurial commands executed by any user in. Options in these files override per- installation options. For example, if installed in /shared/tools/bin/hg, Mercurial will look in. Options in these files apply to all Mercurial commands executed by any user in any directory. Options in these files apply to all Mercurial commands executed. Registry keys contain PATH- like strings, every part of which must reference a Mercurial. If the lines that follow are indented, they are treated as continuations of that entry. Leading whitespace is removed from. Git and Mercurial are the two most popular Distributed Version Control Systems.
Could you make a patch containing Mercurial headers, by 'Export Patch' or 'Email Patch'? We generally accept patches via [email protected], but I think it's simple enough to receive via BTS if you are. Empty lines are skipped. Lines beginning with # or ; are ignored and may be used to provide comments. The inclusion is recursive, which means that included. Filenames are relative to the configuration file in which the %include directive is found. Aliases allow you to define your own commands in terms of other commands (or aliases), optionally including arguments. You can define subsequent aliases using earlier ones. Note. It is possible to create aliases with the same names as existing commands, which will then override the original definitions. This is almost always a bad. Each line has the following format. Example. foo. prefix = hg. Supported arguments. Either * or a URI prefix with or without the scheme part. The authentication entry with the longest matching prefix is used (where * matches. If the prefix doesn't include a scheme, the match is performed against the URI with its scheme stripped as well. Username to authenticate with. If not given, and the remote site requires basic or digest authentication, the user will be prompted for. Password to authenticate with. If not given, and the remote site requires basic or digest authentication, the user will be prompted for. PEM encoded client certificate key file. PEM encoded client certificate chain file. Space separated list of URI schemes to use this authentication entry with. Only used if the prefix doesn't include a scheme. Supported schemes are. They will match static- http and static- https respectively, as well. This would typically be used for newline processing or other localization/canonicalization of files. Filter patterns are globs by default, rooted at the repository root. For example, to match. To match any file ending in . If no specifier is given, pipe: is used by default. The string INFILE is replaced with the name of a temporary file that contains the data to be filtered by. The string OUTFILE is replaced with the name of an empty temporary file, where the filtered data must be written by the command. Use aliases instead). Use the . The command defaults will also be applied to the aliases of the. They are all Boolean and defaults to False. Email address to use in . Comma- separated list of recipients' email addresses. Comma- separated list of carbon copy recipients' email addresses. Comma- separated list of blind carbon copy recipients' email addresses. Cannot be set interactively. Method to use to send email messages. If value is smtp (default), use SMTP (see the SMTP section for configuration). Otherwise, use as name. Normally, setting this to. Comma- separated list of character sets considered convenient for recipients. Addresses, headers, and parts not containing patches of outgoing. HGENCODING, ui. fallbackencoding) succeeds. If. correct conversion fails, the text in question is sent as is. Defaults to empty (explicit) list. To enable an extension, create an entry for it in this section. Disabling this option ensures that the on- disk format of newly created. Mercurial before version 1. Tools matched here will take precedence over the default merge tool. Patterns. are globs by default, rooted at the repository root. Default: the tool name. You can refer to the files being merged as well as the output file through these variables: $base. Default: $local $base $otherpremerge. Attempt to run internal non- interactive 3- way merge tool before launching external tool. Default: True. binary. This tool can merge binary files. Defaults to False, unless tool was selected by file pattern match. Defaults to False, even if tool was selected by file pattern match. Default: False. checkchanged. Check whether outputs were written even though the tool reported success. Default: False. fixeol. Attempt to fix up EOL changes caused by the merge tool. Default: False. gui. This tool requires a graphical interface to run. Default: False. regkey. Windows registry key which describes install location of this tool. Mercurial will search for this key first under HKEY. Default: None. regname. Name of value to read from specified registry key. Defaults to the unnamed (default) value. Default: None. hooks. Commands or Python functions that get automatically executed by various actions such as starting or finishing a commit. Multiple hooks can be run for the. Overriding a site- wide hook can be done by changing its value or setting it to an empty string. For each hook below, the environment variables it is passed are. HG. ID of the first new changeset is in $HG. URL from which changes came is in. HG. ID of the newly created changeset is in $HG. Parent changeset IDs are in. HG. The ID of the newly arrived changeset is in $HG. URL that. was source of changes came is in $HG. ID of first changeset sent is in $HG. Source of operation is in $HG. The contents of the command line are passed as $HG. Hook failure is ignored. The contents of the command line are passed as $HG. If the hook returns failure, the command. Mercurial returns the failure code. Exit status 0 allows the changegroup to proceed. Non- zero status will cause the push, pull or. URL from which changes will come is in $HG. Exit status 0 allows the commit to proceed. Non- zero status will cause the commit to fail. Parent changeset IDs are in. HG. Non- zero status will cause failure. This lets you prevent pull over HTTP or SSH. Source of operation is in. HG. Exit status 0 allows the tag to be created. Non- zero status will cause the tag to fail. ID of changeset to tag is in. HG. Name of tag is in $HG. Changegroup is visible to hook program. Passed the ID of the first new changeset in $HG. Exit status 0 allows the. Non- zero status will cause the transaction to be rolled back and the push, pull or unbundle will fail. URL that was source of changes is. HG. Changeset is visible to hook program. This lets you validate commit message. Exit status 0 allows the commit to proceed. Non- zero status will cause the transaction to be rolled back. ID of changeset is in $HG. Exit status 0 allows the update to proceed. Non- zero status will prevent the update. Changeset ID of first new. HG. If merge, ID of second new parent is in $HG. ID of tagged changeset is in $HG. Name of tag is in $HG. Changeset ID of first new parent is in $HG. If merge, ID of second new parent is in. HG. If the update succeeded, $HG. If the update failed (e. Each hook is called with at least three keyword arguments: a ui object (keyword ui), a repository. Arguments listed as environment variables above are passed as. HG. Comma- separated list of host names that should bypass the proxy. Password to authenticate with at the proxy server. User name to authenticate with at the proxy server. Port to connect to on mail server. Whether to connect to mail server using TLS. User name to authenticate to SMTP server with. If username is specified, password must also be specified. Password to authenticate to SMTP server with. If username is specified, password must also be specified. It's the hostname that the sender can use to identify itself to the MTA. When set to lf or crlf, both files end of lines are ignored. LF (Unix) or CRLF (Windows). The left side is the symbolic name, and the right gives the directory or URL that is the location of the repository. Default is set to repository from which the current repository was cloned. Directory or URL to use when pushing if no destination is specified. In this section description, 'profiling data' stands for the raw data collected during profiling, while. The profiling is done using lsprof. When saving to a file, it should be noted that only the report is saved, and the profiling data is not kept. If the file exists, it is replaced. Default: None, data is printed on stderr. Controls generic server settings. This transfers about 4. CPU on both server and client. Over a LAN (1. 00 Mbps or better) or a very fast WAN, an uncompressed streaming clone is a lot faster (~1. Over most WAN connections (anything slower than about 6 Mbps), uncompressed streaming is slower, because of the extra data transfer overhead. The main exception is the web interface, which automatically uses some safe settings, since it's common to serve repositories from different. The current user is always trusted. To trust everybody, list a user or a group with name. If True, and neither $HGUSER nor $EMAIL has been specified, then the user will be prompted. If no username is entered, the default USER@HOST is used instead. Default is $EDITOR or vi. Default is ISO- 8. This file should be in the same format as a repository- wide . This option supports hook syntax. For details of the ignore file. There are some internal tools available. For more information on configuring merge tools see the merge- tools section. Look for gpatch or patch in PATH if unset. This only makes a difference on systems where the default path separator is not the slash. Windows uses the backslash character (\)).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |