[haiku-development] Re: VOTE: Git or Mercurial (hg) as Haiku's new source control tool

  • From: Phil Garcia <phil@xxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 11 May 2011 22:35:38 -0700

On Wed, May 11, 2011 at 7:22 PM, Richie Nyhus <richienyhus@xxxxxxxxx> wrote:

> > I have to admit that I didn't read the whole discussion. Has someone
> > compiled a pro/contra
> > list of hg and git with target haiku project?
> A pros/cons list was created by Clark Gaebel for GCI at the very end
> of last year.

My personal experience when from moving from SVN to GIT was that learning
curve was not as step as some would describe. GIT is very well documented.
Take a look at this free GIT Community Book:
http://book.git-scm.com/book.pdf for example. There is a dedicated website
just for GIT documentation and resources: http://git-scm.com. And there are
also numerous cheat sheets available, here's a good example:
http://ktown.kde.org/~zrusin/git/git-cheat-sheet-medium.png. GIT is also
real world tested. Linux, another open source operating system, uses it
(granted that Linus wrote it.)

I particularly like using GIT with www.github.com. It provides web based
access to the GIT repositories, commit history, graphs, forks, etc. But even
more valuable is how trivial it is to find, fork and pull from other user's
repositories without necessarily involving the main/official repository.
This can be very helpful when working in small teams that
constantly exchanging source code back and forth for new features and/or bug

Just my two cents...


Other related posts: