With just 100 hundred git branches, I think you're not really using git often and/or to its potential. On a busy coding day, I easily create a few branches. If

With just 100 hundred git branches, I think you're not really using git often and/or to its potential. On a busy coding day, I easily create a few branches. If you also count temporary branches on non-development testing machines (I do driver development on Linux for fun) that can easily reach a dozen. Now what for? I create branches to test merges with other developers code, branches before refactoring my in-progress stuff (so I can go back and pick up the original branch with all its history in case it was a dead-end). I do new branches for simple fixes, tracking down bugs (versioning all test-patches so you can check the next day/week what theories you've already tested is sometimes extremely useful). Sometimes I just do a new branch to get the feel of starting with a clean slate. Once a month or so a look at all the branches lying around and delete those no longer useful. All this is only possible because git branching is _cheap_. Orders of magnitudes cheaper than on any central rcs. And the best part is that git never ever loses anything. git reflog shows you _all_ the states you've gone through to the current one. So all these branches are actually valuable.