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

[Garrett D'Amore]

My biggest concerns about switching to git really relate to tooling.  If
the tools can all accommodate git, then I don't really care.  

	- Garrett

On Wed, 2011-06-22 at 17:54 +0100, Bayard Bell wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Perhaps in the course of the same discussion we might also identify what kind of development workflow we want to adopt going forward? I'm more agnostic about the tools and tend to the view that there are things that we know aren't working well with the way we're using Mercurial at the moment. The attraction of git is defined for me in terms of having a development model that doesn't have some of the pains and weaknesses of what we've been doing, so I'm rather keen for this to be spelled out more in terms of process rather than tools.
> 
> There was a link you shared a while back based on feedback from richlowe that looked pretty juicy. Maybe we could put that into the mix of the current conversation?
> 
> On 22 Jun 2011, at 15:46, Andrzej Szeszo wrote:
> 
> > Hi All
> > 
> > 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.
> > 
> > Cheers,
> > 
> > Andrzej
> > 
> > 1. http://hg-git.github.com/
> > 
> > 
> > _______________________________________________
> > oi-dev mailing list
> > oi-dev at openindiana.org
> > http://openindiana.org/mailman/listinfo/oi-dev
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.12 (Darwin)
> 
> iQIcBAEBAgAGBQJOAh52AAoJEHm5cBpJ87dorawQALNdi0GbSgqmtn3qCD79LWKN
> Ca9dCE6dITfKylVr8m3QoTKJGiITQ0AbhIY/0nY3hFOayyCcI8xESDNb72QtrO8W
> n+1AS7eR8uck6XAfD7G3dFZ1owyYa4CzBbBRzRdztb9vr7yVcuUKcCcq0kmGb0BE
> 9Glzsmyr/nTTFyrE1ihzAiP9UpF1+4Hz8Othbw6gmGfg+iLCVUXoTnWNWpMcDNsr
> AYSb1yP4JYffBlwkgDiVuTdGefFvc7K+RXNGvSm/5PKxl+xzuGe13xOqSDpvTlgS
> a5yRf2OH03E7mscudBh5Adw0/kiKQZGRSO0GIFdf2XfZyZg78N/Y2+rRV9XwaSRP
> vAKJcY7Gus7UREmPhNeW3iN4gq20RICriygGL8gvW/kDTUy3kNr95tnrINboMTFP
> G+AcW7tEscpJfG5siBZY1763zVhEygXJBd7V+si2pC2bOzPdj0hUsEGOU41gksdZ
> UaxT6R/S6hNlnLsBxHxJnCpgkeK3fBfTUCnb9gZoNQA4f31lJ5v2B6AKHTe920Xo
> q1og9Ts5QWwMCKVlmwGzUx7JB0j5PNomv9OCmKU+8o0m02p9veg7EtxL7ab2c3yr
> xqQzqBJpFzI2cxX/7xDMo0b1a0auEMbtDFxVr37sjWDAoT2A6LSkCxgAHIzq5Xkn
> JJwpg3pia/Va3WORU0gw
> =O7+e
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> oi-dev mailing list
> oi-dev at openindiana.org
> http://openindiana.org/mailman/listinfo/oi-dev