How Do You Control Your Source Code?

[eluser]jedd[/eluser]

... but I still feel that the Linus was a big leverage for Git.

Undeniably it was an influencing factor, and got it some exposure, but consider how often you run into BitKeeper shops (or even users) as a sign of how important the chosen SCM for the linux kernel is.

SVN forces you to have a central server, Git allows you to have it if you want, but that central server is not really "central", it's just another branch.

This is so subtle a distinction as to be meaningless, I think. Central is at best a matter of semantics in this instance. Your central server is your primary repository, the place people go for canonical copies of your codebase, etc etc. To me, the central server really is central (even if it happens to also be another branch).

Sometimes I really need it to be central and to have a "commit-access" control for my users.

The [url="http://progit.org/book/ch5-1.html"]Pro-git book[/url] has some bits on how to do this. Commit-access control is easily done using ssh, quite similar to how you'd do it with svn I think.

[quote author="jedd" date="1254276124"]
Seriously,
a) if the quality of your code is at risk because of your choice of SCM, then you have far bigger concerns,
b) I can't see how a distributed SCM could possibly affect the quality of your code.

It's not a matter of affecting quality but of not lowering that quality, of course, the code is made by programmers and they should be responsible for programming right the first time.
[/quote]

As I say, I can not see how an SCM could lower code quality. (Lowering implies affect, of course, but I feel we might be getting lost in the wilderness here.)