[oi-dev] Git as a version control system for new OI projects

[Guido Berhoerster]

Hello,

* Andrzej Szeszo <aszeszo at gmail.com> [2011-06-22 16:48]:
> I would like to ask about your opinions on using Git for new OI
> projects. We've been using Mercurial exclusively so far mainly
> because most of the upstream repositories were using it. There is no
> reason for us to stick with it for new projects though in my
> opinion.
> 
> Using Git for new projects will enable Git and Mercurial users to
> work on the same repository without too much effort. Mercurial
> users, after enabling hg-git extension [1], will be able to use Git
> repository in the same way as normal Mercurial repo, for example:
> 
> $ hg clone git://github.com/joyent/illumos-live.git
> destination directory: illumos-live
> Counting objects: 115, done.
> Compressing objects: 100% (85/85), done.
> Total 115 (delta 13), reused 115 (delta 13)
> importing git objects into hg
> updating to branch default
> 92 files updated, 0 files merged, 0 files removed, 0 files unresolved
> $
> 
> Letting developers to choose their vcs frontend is one nice thing.
> Git's lightweight branches and the way they work are also very
> appealing. Also, more people are familiar with Git than with
> Mercurial so new developers may find it easier to get started with
> the project if its source is managed using Git.
> 
> Let us know what you think.

I don't think having a mix of git and hg is a good idea, ie. hg
being "official" for old repos and git being blessed for new
repos, it'll just cause even more confusion for newcomers.
How about just adding git mirrors for all of hg.oi.o as Illumos
has on github if this really is an issue?
-- 
Guido Berhoerster