This box searches only this space. The box at the upper right searches the entire iPlant wiki.

Skip to end of metadata
Go to start of metadata

(it's important to note that learning Git will not require abandoning Subversion, there is a bi-directional bridge that allows the two to work together [1])

I started hearing about distributed version control systems from my friend Campbell in early March of 2008. I did not really dig in until it was suggested that a group of us present to the Tucson Java User Group in September 2008. Below are the materials that I used to learn Git and prepare for the presentation:

It's really thanks to the Ruby community and GitHub (namely Scott Chacon) that a plethora of quality Git materials exist online. Here's some that I have discovered recently:

If you want to download and install Git, here's some help:

Those working on Windows may want to see this screencast:

It provides a nice introductions to msysGit. An installer for Windows can be downloaded here.

I am always tracking information on Git, so if you want to see what I am consuming you can check out my tagging logs here.

From the Core Software team perspective, many of us use GitX to compare commits and look at branches:

If you're not a fan of the terminal and you're a Mac user - you may want to check this out:

If you find the workflow for Git too confusing, consider using a set of simplified workflow commands like this:

Git supports an awesome set of branching "models" - but there are some best practices out there that people may be interested in:

If you are ready to dive into the low-level details, understanding the "Tale of the Three Tales" is on that path to a deeper and complete understanding of Git:

  • Scott Chacon's article [link]; Scott Chacon's talk [video]

(the deeper and complete understanding here related the results of doing `git reset` with the various available modes/options)

[1] While working at Tree of Life Web project, I played with developing exploratory features in Git by pulling from the tolweb SVN repository. The project was not going to leave the central SVN repository, yet I was still able to use the flexible and power of Git without causing any issues thanks to git-svn. I was also used this during the first couple of months here at iPlant since our prototypes were checked into Subversion

  • No labels
Write a comment…