Why use git for source control?
Andy Balaam, 2013-03-11
What is source control for?
- Backup
- Finding out why
- Multiple simultaneous versions:
- Releases
- Individual changes
Centralised Pros
- Simple
- Good UIs
- Linear history
- "Shelf" (Perforce)
Centralised Cons
- Branching is a "big thing"
- Merging can be difficult (SVN)
- Performance can be poor (SVN)
Why git is better
- Distributed
- Share your code with your friends
- Have more than one "central" repo e.g. staging/smoketested
- Have mini-repos for sub-teams
- Work in mini-branches
- git stash is "Shelf" on steroids
- Fast
Why git is better
- Offline
- Fast
- Don't talk to the server until you're ready
- Full feature set when server is down
- Work in mini-branches
- Merging actually works
- Honestly, it is so fast