Where is mercurial.ini

All you have to do to save it is click "Save private key", and hit "Yes" when it asks if you want to save without a passphrase. Now you need to choose a place to save it and give it a name such as rsa-private. That's it! You should now have successfully created your SSH key and, providing you gave it to Codebase, you should be able to use Mercurial.

All you have to do is load Command Prompt Load the Start menu, then click "Run", type cmd and hit enter , then you can use Mercurial commands as normal. Setting this to prompt will prompt after any merge failure continue or halt the merge process. Setting this to halt will automatically halt the merge process on any merge tool failure.

The merge process can be restarted by using the resolve command. When a merge is halted, the repository is left in a normal unresolved merge state. Tools matched here will take precedence over the default merge tool. Patterns are globs by default, rooted at the repository root.

This section has likely been preconfigured at install time. Use hg config merge-tools to check the existing configuration. Also see hg help merge-tools for more details. If custom labels are not available, these will be local , other , and base , respectively. Options are true , false , keep or keep-merge3. The keep option will leave markers in the file if the premerge fails. The keep-merge3 will do the same but include information about the base of the merge in the marker see internal :merge3 in hg help merge-tools.

If premerge is keep or keep-merge3 , the conflict markers generated during premerge will be detailed if either this option or the corresponding option in the [ui] section is detailed. See the corresponding variable in [ui] for more information.

The alternate key uses the same regname and regappend semantics of the primary key. The most common use for this key is to search for 32bit applications on 64bit operating systems. See hg help pager for details.

If neither pager. When set to lf or crlf , both files end of lines are ignored when patching and the result line endings are normalized to either LF Unix or CRLF Windows. When set to auto , end of lines are again ignored while patching but line endings in patched files are normalized to their original setting on a per-file basis. If target file does not exist or has no end of line, patch line endings are preserved.

This controls how much context the patcher is allowed to ignore when trying to apply a patch. Options are symbolic names defining the URL or directory that is the location of the repository. Options containing colons : denote sub-options that can influence behavior for that specific path. If not defined, the location defined by the path's main entry is used.

When hg push is executed without a -r argument, the revset defined by this sub-option is evaluated to determine what to push. For example, a value of. Revsets specifying bookmarks will not result in the bookmark being pushed.

The following special named paths exist: default The URL or directory to use when no source or remote is specified. See hg help phases for more information about working with phases.

When true, pushed changesets are set to public in both client and server and pulled or cloned changesets are set to public in the client. Allowed values are "ignore", "follow" and "abort". For settings other than "ignore", the phase of the current revision of each subrepository is checked before committing the parent repository.

If any of those phases is greater than the phase of the parent repository e. Two profilers are supported: an instrumenting profiler named ls , and a sampling profiler named stat. In this section description, 'profiling data' stands for the raw data collected during profiling, while 'profiling report' stands for a statistical text report generated from the profiling data.

This profiler works on all platforms, but each line number it reports is the first line of a function. This restriction makes it difficult to identify the expensive parts of a non-trivial function. This profiler is most useful for profiling commands that run for longer than about 0.

Specific to the ls instrumenting profiler. When saving to a file, it should be noted that only the report is saved, and the profiling data is not kept. Specific to the stat sampling profiler. If the file exists, it is replaced. One of callcount , reccallcount , totaltime and inlinetime.

This can help explain the difference between Total and Inline. Can be specified as a float between 0. Only used by the stat profiler. For the hotpath format, default is 0. For the chrome format, default is 0.

The option is unused on other formats. Values format is the same as showmin. Some progress bars only offer indeterminate information, while others have a definite end point. Valid entries for the format field are topic , bar , number , unit , estimate , speed , and item. See hg help revsets for details. Options in this category impact performance and repository size.

This results in better delta selection and improved revlog compression. This option is enabled by default. Turning this option off can result in large increase of repository size for repository with many merges. This config exist for compatibility purpose default to True If you use pushkey and pre-pushkey hooks to control bookmark movement we recommend you migrate them to txnclose-bookmark and pretxnclose-bookmark.

The order of compression engines determines their priority, the first having the highest priority. If a compression engine is not listed here, it won't be advertised to clients. If not set the default , built-in defaults are used. Run hg debuginstall to list available compression engines and their default wire protocol priority. Older Mercurial clients only support zlib compression and this setting has no effect for legacy clients. Over most WAN connections anything slower than about 6 Mbps , uncompressed streaming is slower, because of the extra data transfer overhead.

This mode will also temporarily hold the write lock while determining what data to transfer. Partial clones will still be allowed. This option effectively prevents concurrent pushes. The first matching entry will be streamed to the client. For HTTP transport, the stream will still use zlib compression for older clients.

This requires compatible client version 4. Old client will use 'strict'. The default -1 uses the default zlib compression level, which is likely equivalent to 6.

Setting this option allows server operators to make trade-offs between bandwidth and CPU used. Lowering the compression lowers CPU utilization but sends more bytes to clients. This option only impacts the HTTP server. The default 3 should be significantly faster than zlib while likely delivering better compression ratios.

See also server. Port to connect to on mail server. Method to enable TLS when connecting to mail server: starttls, smtps or none. User name for authenticating with the SMTP server. Password for authenticating with the SMTP server. If not specified, interactive sessions will prompt the user for a password; non-interactive sessions will fail. The hostname that the sender can use to identify itself to the MTA. Groups can be matched in pattern and referenced in replacements.

Relative subrepository paths are first made absolute, and the rewrite rules are then applied on the full absolute path.

If pattern doesn't match the full path, an attempt is made to apply it on the relative path alone. The rules are applied in definition order. See also hg help subrepos. Security note: auditing in Mercurial is known to be insufficient to prevent clone-time code execution with carefully constructed Git subrepos. It is unknown if a similar detect is present in Subversion subrepos.

Both Git and Subversion subrepos are disabled by default out of security concerns. These subrepo types can be enabled using the respective options below. When false, commands involving subrepositories like hg update will fail for all subrepository types. This option only has an effect if subrepos.

See the security note above before enabling Git subrepos. See the security note above before enabling Subversion subrepos. See hg help templates for details. This issue is often encountered when configuring hooks or extensions for shared repositories or servers.

However, the web interface will use some safe settings from the [web] section. This section specifies what users and groups are trusted. The current user is always trusted. When enabled, hg clone may download and apply a server-advertised bundle file from a URL instead of using the normal exchange mechanism. This can likely result in faster and more reliable clones.

This is disabled by default because servers advertising "clone bundles" often do so to reduce server load. If advertised bundles start mass failing and clients automatically fall back to a regular clone, this would add significant and unexpected load to the server since the server is expecting clone operations to be offloaded to pre-generated bundles.

Failing fast the default behavior ensures clients don't overwhelm the server when "clone bundle" application fails. Servers advertising "clone bundles" may advertise multiple available bundles. Each bundle may have different attributes, such as the bundle type and compression format. This option is used to prefer a particular bundle over another. These are strings passed to hg bundle -t.

Server operators may define custom keys. By default, the first bundle advertised by the server is used. Possible value are Boolean "yes" or "no" , or "debug", or "always".

See hg help color for details. If False and one subrepository has uncommitted changes, abort the commit. This file should be in the same format as a repository-wide. Filenames are relative to the repository root. This option supports hook syntax, so if you want to specify multiple ignore files, you can do so by setting something like ignore. For details of the ignore file format, see the hgignore 5 man page.

Possible values are 'text' and 'curses'. This config overrides the interface specified by ui. Possible values are integers or 0 to disable the check.

For more information on merge tools see hg help merge-tools. For configuring merge tools see the [merge-tools] section. The detailed style uses the mergemarkertemplate setting to style the labels. The basic style just uses 'local' and 'other' as the marker label.

One of basic or detailed. See hg help templates for the template format. Defaults to showing the hash, tags, branches, bookmarks, author, and the first line of the commit description. If the encoding of the merge markers is different from the encoding of the merged files, serious problems may occur. Can be overridden per-merge-tool, see the [merge-tools] section. A red vertical line will mark this length. CTRL-E will reflow the current paragraph to the specified line length.

Default: 80 Close After Commit: Close the commit tool after every successful commit. Default: False Push After Commit: Attempt to push to default push target after every successful commit. Default: No push Auto Commit List: Comma separated list of files that are automatically included in every commit. Intended for use only as a repository setting.

Default: None leave blank Auto Exclude List: Comma separated list of files that are automatically unchecked when the status, and commit dialogs are opened.

This setting is used by the Merge, Tag and Backout dialogs. Default: follow Monitor working directory changes: Select when the working directory status list will be refreshed: auto : default let TortoiseHg decide when to refresh the working directory status list.

TortoiseHg will refresh the status list whenever it performs an action that may potentially modify the working directory. Default: auto Confirm adding unknown files: Determines if TortoiseHg should show a confirmation dialog before adding new files in a commit.

If True, a confirmation dialog will be shown. If False, selected new files will be included in the commit with no confirmation dialog.

Default: True Confirm deleting files: Determines if TortoiseHg should show a confirmation dialog before removing files in a commit. If False, selected deleted files will be included in the commit with no confirmation dialog.

Default: none Default Push: Select the revisions that will be pushed by default, whenever you click the Push button. Push all changes in all branches. Default: all Confirm Push: Determines if TortoiseHg should show a confirmation dialog before pushing changesets.

If False, push will be performed without any confirmation dialog. Show the combo if more than one target configured. Default is the working directory. Encoding: Character encoding of files in the repository, used by the web interface and TortoiseHg. When true, pushed changesets are set to public in both client and server and pulled or cloned changesets are set to public in the client.

Contact: Name or email address of the person in charge of the repository. Style: Which template map style to use. Archive Formats: Comma separated list of archive formats allowed for downloading. Port: Port to listen on. Default is 1; set to 0 to disable. Max Files: Maximum number of files to list per changeset. Max Changes: Maximum number of changes to list on the changelog.

Allow Push: Whether to allow pushing to the repository. If empty or not set, push is not allowed. Deny Push: Whether to deny pushing to the repository. If empty or not set, push is not denied. Bypass List: Optional. Comma-separated list of host names that should bypass the proxy. User: Optional. User name to authenticate with at the proxy server. Password: Optional. Password to authenticate with at the proxy server.

To: Comma-separated list of recipient email addresses. Cc: Comma-separated list of carbon copy recipient email addresses. Bcc: Comma-separated list of blind carbon copy recipient email addresses. 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.

Default: Local Hostname: Hostname the sender can use to identify itself to the mail server. Strict does no normalization. Auto does per-file detection, and is the recommended setting. Default: strict Git Format: Use git extended diff header format. Default: False. MQ Git Format: When set to auto , mq will automatically use git patches when required to avoid losing changes to file modes, copy records or binary files. If set to keep , mq will obey the [diff] section configuration while preserving existing git patches upon qrefresh.

If set to yes or no , mq will override the [diff] section and always generate git or regular patches, possibly losing data in the second case. Default: auto No Dates: Do not include modification dates in diff headers. Show Function: Show which function each change is in.

Ignore White Space: Ignore white space when comparing lines.