1. Paul McGrath

2.  Speedy Input  Speedy Visualisation  Speedy Workflow

3.  git push master~2:master  git pull –rebase  (git fetch origin, git rebase origin/master)

4.  Interactive rebase (rebase –i)

6.  In ~/.bashrc and ~/bin  My editor is much easier to use for interactive rebase, commit –amend etc.  Share your setup – it’s all config files

8.  ~/.bashrc:

10.  Features tied together  Can’t unpick the log  Branching from untested code  Your product is the sum of independent features  Features can be easily removed  You have a safe point to branch from

11.  Git docs: Branching strategy (http://git- scm.com/book/en/v2/Git-Branching-Branching- Workflows)http://git- scm.com/book/en/v2/Git-Branching-Branching- Workflows

13.  http://scottchacon.com/2011/08/31/github- flow.html http://scottchacon.com/2011/08/31/github- flow.html  git merge develop  Keep it as light-weight as possible  …Yeah, but what about conflicts? DEVELOP MASTER MY LOVELY FEATURE

14.  Avoiding conflicts  Small commits  merge safe point into branches  Even better… rebase!  …Yeah, but I don’t want to see all these branches all over our repo…