Example: foo. If the prefix doesn't include a scheme, the match is performed against the URI with its scheme stripped as well, and the schemes argument, q. Username to authenticate with. If not given, and the remote site requires basic or digest authentication, the user will be prompted for it. Password to authenticate with. 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 http and https. They will match static-http and static-https respectively, as well. Default: https. If no suitable authentication entry is found, the user is prompted for credentials as usual if required by the remote.
Filters consist of a filter pattern followed by a filter command. Filter patterns are globs by default, rooted at the repository root. For example, to match any file ending in.
To match any file ending in. The filter command can start with a specifier, either pipe: or tempfile:. If no specifier is given, pipe: is used by default. A pipe: command must accept data on stdin and return the transformed data on stdout. For this, use the "smart" converters which check for binary files: [extensions] hgext. Don't use them. Use aliases instead Use the [defaults] section to define command defaults, i.
The command defaults will also be applied to the aliases of the commands defined. They are all Boolean and defaults to False. 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. Otherwise, use as name of program to run that acts like sendmail takes -f option for sender, list of recipients on command line, message on stdin.
Comma-separated list of character sets considered convenient for recipients. If correct conversion fails, the text in question is sent as is. Defaults to empty explicit list.
Order of outgoing email character sets: 1. To enable an extension, create an entry for it in this section. To explicitly disable an extension that is enabled in an hgrc of broader scope, prepend its path with! Enabled by default. Disabling this option will allow you to store longer filenames in some situations at the expense of compatibility and ensures that the on-disk format of newly created repositories will be compatible with Mercurial before version 0.
Disabling this option ensures that the on-disk format of newly created repositories will be compatible with 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: 0. Default: the tool name. 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 gui This tool requires a graphical interface to run.
Default: False regkey Windows registry key which describes install location of this tool. 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 same action by appending a suffix to the action. Overriding a site-wide hook can be done by changing its value or setting it to an empty string. Hook failure is ignored. To generate a unique key, PuttyGen needs you to move the mouse curser randomly over the area directly below the progress bar, so just do that and watch the progress bar fill all the way up.
When it's finished, it will have generated two keys: a Public Key and a Private Key. The Public Key the one that it displays on the screen is the one that you need to give to Codebase just copy it from the screen then follow the instructions in the Getting Started guide to paste it into your Codebase profile, to allow full access to any Hg repositories that you are assigned to.
The Private Key has to be be used by Mercurial to allow you to connect to Codebase. To do this, it must first be saved from PuttyGen to a sensible location it doesn't matter where, just best to keep it where you know where it is. For storing the login IDs, it's usually a good idea to do what you did, especially if you have a different username for each project you work on.
Otherwise, you could create a Mercurial. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Mercurial win instal: no ini files Ask Question. Asked 11 years, 6 months ago. Active 11 years, 6 months ago. Viewed 9k times. Improve this question. Marwan Marwan 1, 1 1 gold badge 11 11 silver badges 20 20 bronze badges. Type set to see a list of all current values. Add a comment.
0コメント