This chapter describes the three most popular Mercurial extensions for interoperating with foreign VCS systems. See also Repository Conversion
This extension modifies the remote repository handling so that repository paths that resemble:
cause operations on the named p4 client specification on the p4 server. The client specification must already exist on the server before using this extension. Making changes to the client specification Views causes problems when synchronizing the repositories, and should be avoided.
Five built-in Mercurial commands are overridden.
If the destination repository name starts with p4:// then this reports files affected by the revision(s) that are in the local repository but not in the p4 depot.
If the destination repository name starts with p4:// then this exports changes from the local repository to the p4 depot. If no revision is specified then all changes since the last p4 changelist are pushed. In either case, all revisions to be pushed are foled into a single p4 changelist. Optionally the resulting changelist is submitted to the p4 server, controlled by the --submit option to push, or by setting **perfarce.submit** to True. If the option **perfarce.keep** is False then after a successful submit the files in the p4 workarea will be deleted.
If the source repository name starts with p4:// then this imports changes from the p4 depot, automatically creating merges of changelists submitted by hg push. If the config option **perfarce.keep** is False then the import does not leave files in the p4 workarea, otherwise the p4 workarea will be updated with the new files.
If the source repository name starts with p4:// then this reports changes in the p4 depot that are not yet in the local repository.
If the source repository name starts with p4:// then this creates the destination repository and pulls all changes from the p4 depot into it.
When the perfarce extension is enabled, it adds a start revision configurable option to the clone tool, and a Perforce menu to the Repository Explorer. The menu has two items:
Finds the tip Perforce changelist in your local repository and selects it in the changelog window.
Detects pending Perforce changelists that have been "push"ed to your Perforce client but have not been submitted, or have not been pulled back. This opens the pending changelist dialog so that you can view these pending changelists and either submit or revert them.
Perfarce comes bundled with TortoiseHg 1.0 Windows installers, so you enable perfarce by simply adding it to your Mercurial.ini or a repository’s hgrc like this:
hgsubversion, as it’s name implies, allows you to use Mercurial as a client to a Subversion server. It can also be used to do straight conversions of Subversion repositories into Mercurial.
TortoiseHg Windows installers come with the python-svn bindings that hgsubversion requires, so one only needs to clone the hgsubversion repository to your local computer:
hg clone http://bitbucket.org/durin42/hgsubversion/ C:\hgsvn
Then enable the extension in your Mercurial.ini file, specifying the hgsubversion folder inside the cloned repository:
[extensions] hgsubversion = C:\hgsvn\hgsubversion
You can verify that worked by typing hg help hgsubversion
See the hgsubversion wiki for details of use.
When doing a clone of a Subversion server, it is highly recommended to clone only the first few revisions, then pull the rest. Clone’s failure behavior is to delete the entire incomplete cloned repository. Pull is much more forgiving.
Imported Subversion changesets will display the original Subversion checkin number in the Repository Explorer browser.
hg-git, as its name implies, allows you to use Mercurial as a client to a git server. It can also be used to do straight conversions of Git repositories into Mercurial.
TortoiseHg Windows installers come with the python-git bindings (named dulwich) that hg-git requires, so one only needs to clone the hg-git repository to your local computer:
hg clone http://bitbucket.org/durin42/hg-git/ C:\hg-git
Then enable hggit and bookmarks in your Mercurial.ini file:
[extensions] bookmarks = hggit = C:\hg-git\hggit
You can verify that worked by typing hg help hggit
See the hggit documentation for details of use.
Beware the ‘incoming’ command appears broken when speaking with git repositories, and ‘outgoing’ does not show much useful info. So you are restricted to simple push and pull commands (not uncommon for extensions that speak with external revision control tools).