Converts a Darcs repository into a Git repository. Supports incremental updates, i.e., you can pull new patches from the source repository or import a large repository in steps.
An alternative and similar tool is darcs-fastconvert, which may or may not suit your needs better.
(Use darcs-to-git --help to display the latest usage instructions.)
Create an empty directory that will become the new git repository
From inside that directory, run this program, passing the location of the local source darcs repo as a parameter
The program will git-init the empty directory, and migrate all patches in the source darcs repo into commits in that repository.
Thereafter, incremental patch conversion from the same source repo is possible by repeating step 2.
--patches N: only import N patches.
--email-address ADDRESS: darcs-to-git tries to reconstruct the email address from the darcs patch. In cases this is not possible, a default will be picked by Git. This is usually the one in ~/.gitconfig. This option allows you to specify another default (without having to to modify ~/.gitconfig.)
--list-authors: Outputs a list of authors in the source repository and how they will appear in the git repository and quits. The output will be lines like this:
Jane@example.com: Jane <Jane@example.com>
This means that the darcs author Jane@example.com will be translated to git-author Jane with email addressJane@example.com. You can use the output of this command as a starting point for the input for --author-map.
--author-map FILENAME: Allows translations from darcs committer name to Git committer name. The input is a YAML map. For an example see the output of --list-authors. The author map will be stored in the repository and will be re-used for future imports.
When darcs-to-git pulls a conflicting patch it will revert the state of the repository to the state before the conflict. This will also remove any local changes to your repository, including git commits! You should therefore not commit to the branch you import to, but instead work in a different branch. You can rename your master branch after import using:
$ git branch -m darcs_import
darcs-to-git creates a full copy of the original repository in addition to the Git repository; this can lead to considerable space usage. You can save space by treating the copied Darcs repository as a branch by running
$ darcs optimize --relink --sibling /old-repo/dir
inside the new repository.
How to Make a Git Mirror of a Darcs Repository
In this article I discuss techniques for migrating source code repositories from darcs to git. I describe two approaches that failed for me, and introduce a new tool that I was able to use successfully with my own projects, and that can be used to create git mirrors of active darcs repositories.
I’ve been a big fan of darcs for over two years, and have used it exclusively for my personal projects. However, in recent times I have been increasingly drawn in by the community and toolset that is growing around git, and I’ve naturally wanted to migrate some of my darcs repositories to git.
The first tool I tried, darcs2git, uses a low-level git component called git-fast-import to efficiently slurp data into git, but when I tried to use it with the latest git at the time of writing, git-fast-import choked on the binary data passed to it by darcs2git. Game over.
Tailor, the Swiss Army Knife of inter-VCS synchronisation, has helped me several times in the past to migrate 80% of one VCS’ contents into a new VCS-du-jour, ultimately leading me to abandon it or file bug reports. Your mileage might vary, depending on the source and target VCSes you try it with.
The key to tailor’s versatility is also its Achilles heel - it has a standardised notion of a changeset, into which intermediate form every source changeset is transformed. This notional changeset can contain renames of files and directories, additions, deletions of files, and suchlike.
When I tried to use tailor to convert my darcs repos to git, it became stuck on certain changesets, apparently due to it misunderstanding some of the move/rename cases in the source darcs changesets, and therefore being unable to replay them into the working copy it uses for migration.
A new approach
I decided to write my own naïve conversion script, which would initialize a dual darcs/git repository in a working directory set aside for migration, then gradually pull changes from a source darcs repo and record each changeset wholesale into the git repository.
Using tricks from darcs2git, tailor and git-svn, I was able to do this pretty easily, and my script even supports incremental importing from an active darcs repository, which would allow it to be used for maintaining public git mirrors of darcs repositories.
Unoriginally dubbed darcs-to-git, and written in ruby, the code can be found (and tracked) here:
darcs-to-git inserts tags into the comments of the git commits it produces, containing the globally unique darcs patch ID from which the commit originated. Having seen this technique used by the excellent git-svn, this seemed the neatest approach for making incremental migration of new darcs patches possible.
Branches, and multiple source darcs repositories
darcs-to-git can only import changesets from a single darcs repository, which essentially means there is no support for importing the implicit branching that results from darcs’ “cherry-picking” nature. It should be possible to add such support, however.
Each darcs repository is essentially a unique branch, consisting of a dependency-ordered bag of changesets that individually may or may not appear in other darcs repositories. By comparing the patch list of two darcs repositories starting with their earliest (common) revision, it should be possible to determine the points at which to create git branches, and use git-merge and/or git-cherry-pick to propagate later common patches between branches.
Patches to darcs-to-git for this or any other worthwhile purpose are welcome.