Issues

Issue #31 resolved

Migration to git?

Takeshi Abe
created an issue

This is not an issue, but just an idea.

I wonder if it would be nice to migrate the gd repository to git, because mercurial lacks some useful features git has, e.g. http://www.emilsit.net/blog/archives/git-is-more-usable-than-mercurial/. And I think GD developers are all familiar with git :)

For instruction to convert hg repositories to git on bitbucket, you may find http://blog.bitbucket.org/2011/10/05/converting-hg-repositories-to-git/.

But hg-fast-export is an easier alternative to do that: http://hedonismbot.wordpress.com/2008/10/16/hg-fast-export-convert-mercurial-repositories-to-git-repositories/ It can maintain all logs as well as tags in the original repository.

Thank you for your consideration.

Comments (5)

  1. Pierre Joye

    hi!

    yes, the more I think about it the more I want to to use git as well :)

    I also have created an organization for GD, easier to have more members working on GD and managing the repos.

  2. Takeshi Abe reporter

    yes, the more I think about it the more I want to to use git as well :)

    Thank you for your support. Feel free to ping me if you want any help for this task.

    I also have created an organization for GD, easier to have more members working on GD and managing the repos.

    Ah great, now I finally noticed the "libgd" team!

  3. Pierre Joye

    the move to libgd org should happen in the next days. Web sites will be there 1st using git.

    I have to find a way to move the libgd and tools repositories to git without loosing commits history, or duplicate them and add a note for past commits.

  4. Takeshi Abe reporter

    Hi Pierre,

    I have exported the gd-libgd repository to a git repository by hg-fast-export. You can see & check it on https://bitbucket.org/tabe/gd-libgd-git, which is prepared temporarily only for this issue.

    Note that all of the logs saved in the history have been migrated as expected, except bogus author's mail addresses in the commits come from the original CVS repository, such as "pajoye devnull@localhost".

    I left them as is, but we can repair them by git-filter-branch before pushing commits to new repository.

  5. Log in to comment