An interactive script to set up the basic Git parameters

Gitslave creates a group of related repositories—a superproject repository and a number of slave repositories—all of which are concurrently developed on and on which all git operations should normally operate; so when you branch, each repository in the project is branched in turn. Similarly when you commit, push, pull, merge, tag, checkout, status, log, etc; each git command will run on the superproject and all slave repositories in turn. This sort of activity may be very familiar to CVS and (to a lesser extent) Subversion users. Gitslave's design is for simplicity for normal git operations.

So you've made it through Git 102, and you wanted more. Git 102 was more of a justification for some of git's trickery, and a way for me to express my philosophies for using version control. Now that you're through with that, let's see if we can figure out some of git's less known features.

The svn vs. git article I wish I'd written: #i_aint_gonna_need_it

A humourous commit message generator

Use the frequncy of issuing git commands as your hint for what to create aliases for.

RT @springsource: SpringSource Team Blog: Social Coding and Git: How to Merge Without Fear #spring

#DCath regarding @PanosJee #git talk, check out gource and git-ftp

Broadcast Git repos over Bonjour

'Aha! Moments When Learning #Git' | BetterExplained [Git operations as virtual file and directory changes]

Martin Fowler talks about using feature branches in version control

Using Git while trapped using the awful ClearCase version control system.

Instructions on using rebase with the Git version control system

Resin web server using Git to deploy apps across a cluster

Filter-branch a repo then clean up old objects by expiring them and pruning them off immediately. Pro trick.

Phone interview with Andy Glover on Git

If you make the update to Git 1.7.2 (or now, 1.7.3), do check out these tips .

Another good Git doc :

Convert SVN repositories to Git repositories and maintain the SVN tags as Git tags. git-svn does not maintain this fidelity and turns SVN tags into Git branches.

Enjoyed this simple guide to #Git, with #SVN parallels:

A description of working with Git and Subversion

Experimental fork of Pieter's nice git GUI for OS X. Includes: sidebar, fetch, pull, push, add remote, merge, cherry-pick, rebase, clone, clone to.

Test based GUI for Git

Git support for NetBeans