> I usually want to make software, together with my team 1. Small-scale history: Developers make mistakes. When things go wrong, a clean history of small, incr

> I usually want to make software, together with my team 1. Small-scale history: Developers make mistakes. When things go wrong, a clean history of small, incremental changes is priceless. Git helps you craft such a history. It's not about what actually happened. It's about helping you solve future problems. 2. Large-scale history: large projects branch. Especially commercial ones, where you need to support old versions, or maybe have custom versions for laaarge customers. Git handles this well. And it's good at helping you get identical changes into multiple branches without loosing track. > and I bet this holds for 90% of GitHub's paying customers. 90% of everything is crap ;)