Hacker News Reader

tux1968

That was the original value proposition made by Linus when he first create Git. This was largely out of necessity because it all happened over a very few short days in the panic of losing BitKeeper support for the Kernel.

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.

View on HN

And still, Git, compared to most centralized VCSes, forces you to consciously design the versioning workflow. Where will the repositories be, who pushes where under what circumstances, what repo makes the golden releases, will you merge the upstream into feature branches or will you rebase, all that.

That makes it harder to introduce Git in an organization where nobody brings along enough Git experience to design all that upfront.

It's easy to use Git in exactly the same way you would use SVN with a single central repository.

Just grab the gitpro book and spend 3 minutes copying one of the diagrams and the description (or use the website).

I understand what you're saying: I have helped some friends who were that guy trying to bring it in.

Looking into what you said, that is what happened.

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".

Reply on news.ycombinator.com