7. Extensions

This chapter describes Mercurial extensions that are shipped with TortoiseHg binary packages for Windows. These external extensions are included as a convenience to users, so they can be easily enabled as soon as they are needed.

7.1. Hgfold

hgfold is a Mercurial extension that helps Windows users deal with filename case collisions on VFAT and NTFS.

It adds options to the following Mercurial commands. Type hg help <command> for more information:

up    - allows you to update to a revision with filename collisions
merge - allows you to merge with a changeset that would create filename collisions

The extension does not currently do anything to prevent filename collisions. See discussion on the Mercurial Wiki


To test the use of this plugin, you can specify it on the Mercurial command line like this:

hg --config "extensions.fold=" status

You may want to add it to your Mercurial.ini or a repository’s hgrc like this:


If you do this, you can omit the –config command-line option.


Like all merge operations, fold.py has to change the parents of the working directory. It is still in early testing, so use with caution.

If you get an error about an unknown changeset after running hg recover try hg debugsetparents <number of tip revision>. You can find the number of the tip revision by running hg log -l 2.

7.2. Hgcr-gui

CodeReview management tool

  • This extension allows you to manage reviews for your code in any project you like.
  • It helps to keep the review management inside the mercurial.
  • One can add files to the review, remove them and notify reviewr that files are ready for review.
  • The reviewer can mark the code as ‘completed’ review cycle and return the message to the developer.
  • The project manager can check the review status - which files are reviewd and which are not yet.
  • The extension will automatically spot the files that were changed since their last review and notify about that.
  • This extension uses GUI from TortoiseHg but also implements command line interface.
  • Code review database is stored in .code-review file in your repository root directory as a map of file and revision when review was done.



Code Review Plugin (requires Mercurial 1.3.x and TortoiseHg 0.9)


 -c --complete  Mark CR as complete
 -a --add       Add files to CR list
 -r --remove    Remove files from CR list
 -l --list      Print files in CR list

use "hg -v help cr" to show global options


To start GUI don’t give any options.

More Details

  • I’ve implemented the review around files and not changesets, because at the end, I want to be able to tell for the specific project if all the files went through code review process or not - the project status.
  • Suppose you have some project that you are in charge and many developers do write code for it. And there is a group of reviewrs that review the developers code.
  • Is is very difficult to keep track of changes developers do, but simple to find out what files have already been reviewd (by reviewers) and what were not.
  • Using this extension, Developer can mark his files (when finished development process) as “Ready for review” and send notice to reviewer.
  • Reviewer will pick up the changeset (because changesets are stored in the code review database) and perform code review (put notes inside the developer’s code).
  • Afterwards Reviewr will mark the files as “Review Completed” and return the notice to the developer.
  • The project manager can follow every time what is going on with his/her project.


You may want to add it to your Mercurial.ini or a repository’s hgrc like this:


7.3. Mercurial-Keyring

Keyring extension uses services of the keyring library to securely save authentication passwords (HTTP/HTTPS and SMTP) using system specific password database (Gnome Keyring, KDE KWallet, OSXKeyChain, dedicated solutions for Win32 and command line).

What it does

The extension prompts for the HTTP password on the first pull/push to/from given remote repository (just like it is done by default), but saves the password (keyed by the combination of username and remote repository url) in the password database. On the next run it checks for the username in .hg/hgrc, then for suitable password in the password database, and uses those credentials if found.

Similarly, while sending emails via SMTP server which requires authorization, it prompts for the password on first use of given server, then saves it in the password database and reuses on successive runs.

In case password turns out incorrect (either because it was invalid, or because it was changed on the server) it just prompts the user again.


First, the extension must be enabled in your Mercurial.ini file as:


Password backend configuration

The most appropriate password backend should usually be picked automatically, without configuration. Still, if necessary, it can be configured using ~/keyringrc.cfg file (keyringrc.cfg in the home directory of the current user). Refer to keyring docs for more details.


On Windows XP and above, your encrypted passwords are stored in the credentials subsystem using CredRead and CredWrite


On Windows 2K, the encrypted passwords are stored in the system registry under HKCU\Software\Mercurial\Keyring.

Repository configuration (HTTP)

Edit repository-local .hg/hgrc and save there the remote repository path and the username, but do not save the password. For example:

myremote = https://my.server.com/hgrepo/someproject

myremote.schemes = http https
myremote.prefix = my.server.com/hgrepo
myremote.username = mekk

Simpler form with url-embedded name can also be used:

bitbucket = https://User@bitbucket.org/User/project_name/


If both username and password are given in .hg/hgrc, extension will use them without using the password database. If username is not given, extension will prompt for credentials every time, also without saving the password. So, in both cases, it is effectively reverting to the default behaviour.

Consult [auth] section documentation for more details.

Repository configuration (SMTP)

Edit either repository-local .hg/hgrc, or ~/.hgrc (the latter is usually preferable) and set there all standard email and smtp properties, including smtp username, but without smtp password. For example:

method = smtp
from = Joe Doe <Joe.Doe@remote.com>

host = smtp.gmail.com
port = 587
username = JoeDoe@gmail.com
tls = true

Just as in case of HTTP, you must set username, but must not set password here to use the extension, in other cases it will revert to the default behaviour.


Configure the repository as above, then just pull and push (or email) You should be asked for the password only once (per every username + remote_repository_url combination).

Table Of Contents

Previous topic

6. Recovery

Next topic

8. Frequently Asked Questions

This Page