Ask HN: Is Git an appropriate SCM for large enterprise software companies?

All of the large companies that I've worked at in the past 10+ years have eventually transitioned their SCM into either Clearcase or Perforce (usually Perforce). The engineering VPs who make these decisions are pretty smart, and have a lot of exposure to SCMs, and are not unfamiliar with the advantages of DVCS. Recently, a colleague took over a engineering management position at a smaller (300 employee) company that had decided to try and use git as their SCM. They currently have seven build engineers w/25 software developers, a ratio that is severely out of whack (My current org managed to get up to 100 developers with just a single build engineer). What's worse, is that when this manager asked to branch the tree, he got some pushback - the effort was not insignificant. Git seems to work well when you have a small number of branches moving forward (linux kernel), but, for enterprises where you might have dozens of long-lived branches, each of which needs collections of fixes checked into all the branches - Perforce/Clearcase seem to be a better tool for the job. Anybody else have a different experience?