Hg-Git Mercurial Plugin
This is the Hg-Git plugin for Mercurial, adding the ability to push and pull to/from a Git server repository from Hg. This means you can collaborate on Git based projects from Hg, or use a Git server as a collaboration point for a team with developers using both Git and Hg.
The Hg-Git plugin can convert commits/changesets losslessly from one system to another, so you can push via an Hg repository and another Hg client can pull it and their changeset node ids will be identical - Mercurial data does not get lost in translation. It is intended that Hg users may wish to use this to collaborate even if no Git users are involved in the project, and it may even provide some advantages if you're using Bookmarks (see below).
This plugin is implemented entirely in Python - there are no Git binary dependencies, you do not need to have Git installed on your system. The only dependencies are Mercurial and Dulwich. The plugin is known to work on Hg versions 1.3 through 1.5 and requires at least Dulwich 0.6.0.
You can clone a Git repository from Hg by running
hg clone [url]. For
example, if you were to run
$ hg clone git://github.com/schacon/hg-git.git
hg-git would clone the repository down into the directory 'munger.git', then convert it to an Hg repository for you.
If you want to clone a github repository for later pushing (or any other repository you access via ssh), you need to convert the ssh url to a format with an explicit protocol prefix. For example, the git url with push access
(Mind the switch from colon to slash after the host!)
Your clone command would thus look like this:
$ hg clone git+ssh://firstname.lastname@example.org/schacon/hg-git.git
If you are starting from an existing Hg repository, you have to setup
a Git repository somewhere that you have push access to, add it as
default path or default-push path in your .hg/hgrc and then run
push from within your project. For example:
$ cd hg-git # (an Hg repository) $ # edit .hg/hgrc and add the target git url in the paths section $ hg push
This will convert all your Hg data into Git objects and push them up to the Git server.
Now that you have an Hg repository that can push/pull to/from a Git
repository, you can fetch updates with
$ hg pull
That will pull down any commits that have been pushed to the server in the meantime and give you a new head that you can merge in.
Hg-Git can also be used to convert a Mercurial repository to Git. As Dulwich doesn't support local repositories yet, the easiest way is to setup up a local SSH server. Then use the following commands to convert the repository (it assumes your running this in $HOME).
$ mkdir git-repo; cd git-repo; git init; cd .. $ cd hg-repo $ hg bookmarks hg $ hg push git+ssh://localhost:git-repo
The hg bookmark is necessary to prevent problems as otherwise hg-git pushes to the currently checked out branch confusing Git. This will create a branch named hg in the Git repository. To get the changes in master use the following command (only necessary in the first run, later just use git merge or rebase).
$ cd git-repo $ git checkout -b master hg
To import new changesets into the Git repository just rerun the hg push command and then use git merge or git rebase in your Git repository.
Hg Bookmarks Integration
If you have the bookmarks extension enabled, Hg-Git will use it. It will push your bookmarks up to the Git server as branches and will pull Git branches down and set them up as bookmarks.
Clone this repository somewhere and make the 'extensions' section in
~/.hgrc file look something like this:
[extensions] hgext.bookmarks = hggit = [path-to]/hg-git/hggit
That will enable the Hg-Git extension for you. The bookmarks section is not compulsory, but it makes some things a bit nicer for you.
hg-git keeps a git repository clone for reading and updating. By default, the
git clone is the subdirectory
git in your local Mercurial repository. If you
would like this git clone to be at the same level of your Mercurial repository
.git), add the following to your
[git] intree = True