Git Version Control

It would be nice for the project to use Git.
I've been using git-svn internally, which only really supports linear histories. Using Git for the project's VCS might accelerate development, given it's current popularity and ease of branching.
Pull requests also make it easier to integrate contributions.


There's no need to sell me on Git; MOC development is based around it (via git-svn). There have been e-mail discussions in the background over the past two weeks around moving to Git, and the mood is very positive. But time is the main impediment (as usual); it's not like there is a large team behind MOC to absorb the work.

I agree with everything you say, but there's a large backlog of uncommitted contributions which are now being worked through. Changing VCSs in the middle of that is an unnecessary distraction just at the moment which would further delay wished for end-user features.

However, there is an interim solution which may be available to us and is under consideration.

Great to hear. Thanks.

I've been working on a small patch to MOC which I wanted to put online somewhere and as a heavy user of it GitHub seemed like the right place for me. I did not find any 'clean' mirror of MOC's subversion repository on GitHub that I could fork to my personal account. With 'clean' I mean a mirror without unofficial additions. So I set up such a mirror under a new organization called 'console-tools' ('moc' was already taken as a username/organization name). I do not plan to add any commits to this repository myself, just to keep it in sync with the SVN for the moment.

The repository has been cloned using the 'svn2git' tool to preserve the commit history. I understand that you consider migrating to Git a distraction at the moment and working on it does not have priority. Anyway I wanted to let you and the community know about this. Should you be interested I will of course also make you admin of that repository/organization. Here's the link:

If you find this useful, please let me know. I'm available for making the import from SVN optimal. One thing that's broken for now are the commit author email addresses of the three SVN committers (because I don't know which ones to use).

Thanks for that, "sebastian". Unfortunately you've come into the middle of an ongoing effort. I'll need to discuss things with you by e-mail.