fwiw, from my pov

if you look around github and bitbucket people started their clones there already
those repos contain patches (some of them are worthwhile pulling over)

also lifecycle/review of patches from community is easier already with plain github

so from where I stand I did like the tools one gets out of box with git (and yes, I am aware we could have continued with mercurial e.g. on bitbucket, or on code.google.com , but let's do the git now)

otherwise if it's hg or git doesn't really matter

--
L

On 8.1.2013 17:21, Trond Norbye wrote:

Hi Conrad,

OpenGrok grew out of opensolaris.org <http://opensolaris.org>, which used (and still use) mercurial as the distributed SCM system. I don't have that much problems with mercurial, but I do miss the flexibility with patch management we've got with git. Its been a long time since I followed "whats new" with mercurial, so these functionalities may be available there as well.

My main motivation for using git is that I want us to use gerrit in the future (I just need to figure out if there is somewhere we can get the service, or if we need to set up a gerrit server ourselves).

Github is a popular hosting service, and by getting the code there we're also hoping it will lower the bar for people to contribute to the project (just send us a pull request etc).

Cheers,

Trond


On Tue, Jan 8, 2013 at 4:28 PM, Conrad Dean <conrad.p.d...@gmail.com <mailto:conrad.p.d...@gmail.com>> wrote:

    Hey Trond,

    I'm excited for the change over to git.  What were the factors in
    the decision?  I've noticed a lot of  open source projects that
    are on CVS or svn generally pick one distributed system and stick
    to it.  I'm curious as to what drove the move from one distributed
    scm to another.

    In any case, I'm really looking forward to following OpenGrok on
    github now.

    -Conrad


    On Tue, Jan 8, 2013 at 6:51 AM, Trond Norbye
    <trond.nor...@gmail.com <mailto:trond.nor...@gmail.com>> wrote:

        Hi!

        We've been using Mercurial as the source control management
        system for OpenGrok for some years now, and for most of the
        things we've been doing its been working fine.

        As of today we want to move the development of OpenGrok from
        Mercurial to Git (and hopefully get a gerrit server
        up'n'running (see: http://code.google.com/p/gerrit/ ) to make
        it easier for more people to get involved in the development
        of OpenGrok (and make it easier for us to merge patches etc).

        Please note that the _only_ thing that change is the location
        of the master source repository. As of today please use:
        https://github.com/OpenGrok

        The new method to check out the git repository is now:

        git clone git://github.com/OpenGrok/OpenGrok
        <http://github.com/OpenGrok/OpenGrok>

        when you've got a patch you'd like to submit to us you can
        either do that via a pull request on github, or send the patch
        to the mailing list. You create the patch(es) from:

        git format-patch HEAD^
        (HEAD^ creates a patch file from the latest patch in your
        repository).

        Happy hacking folks!

        Cheers,

        Trond

        _______________________________________________
        opengrok-discuss mailing list
        opengrok-discuss@opensolaris.org
        <mailto:opengrok-discuss@opensolaris.org>
        http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss





--
Trond Norbye


_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss

Reply via email to