https://github.com/purcell/darcs-to-git

Convert/mirror darcs repos into git repos
https://github.com/purcell/darcs-to-git

Last synced: 1 day ago
JSON representation

Convert/mirror darcs repos into git repos

• Host: GitHub
• URL: https://github.com/purcell/darcs-to-git
• Owner: purcell
• License: mit
• Created: 2008-05-05T07:59:31.000Z (over 16 years ago)
• Default Branch: master
• Last Pushed: 2024-11-07T07:31:02.000Z (2 months ago)
• Last Synced: 2025-01-12T10:05:37.778Z (9 days ago)
• Language: Ruby
• Homepage: http://www.sanityinc.com/articles/converting-darcs-repositories-to-git
• Size: 72.3 KB
• Stars: 96
• Watchers: 7
• Forks: 20
• Open Issues: 4
• Metadata Files:
  • Readme: README.markdown
  • License: LICENSE

Awesome Lists containing this project

README

        
darcs-to-git

============

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.

Usage

-----

(Use `darcs-to-git --help` to display the latest usage instructions.)

1. Create an *empty* directory that will become the new git repository

2. 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.

Options

-------

 * `--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:

   ```

   [email protected]: Jane 

   ```

   This means that the darcs author `[email protected]` will be

   translated to git-author `Jane` with email address

   `[email protected]`.  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.

Known issues

------------

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](http://wiki.darcs.net/BestPractices#how-to-create-a-branch) by

running

    $ darcs optimize --relink --sibling /old-repo/dir

inside the new repository.

Acknowledgements

----------------

Written and maintained by Steve Purcell, with some improvements by

Thomas Schilling, Jonathon Mah and others.



[💝 Support this project and my other Open Source work via Patreon](https://www.patreon.com/sanityinc)

[💼 LinkedIn profile](https://uk.linkedin.com/in/stevepurcell)

[✍ sanityinc.com](http://www.sanityinc.com/)