Git isn't an SCM, it's a SCM building toolkit.
You personally do not have to understand all the parts, but you do need someone to build a SCM for you out of it and tell you what the parts are then.
You personally do not have to understand all the parts, but you do need someone to build a SCM for you out of it and tell you what the parts are then.
However it is no longer true. Git is very much a SCM and is being developed as an independent tool, not just as a platform for tool development.
I'd always heard that said about the tool we used today to point out "It does way too much for a single SCM, you have to find what YOU need a SCM to do and use that".
That makes it harder to introduce Git in an organization where nobody brings along enough Git experience to design all that upfront.
I understand what you're saying: I have helped some friends who were that guy trying to bring it in.