Vistaus wrote:1 How many times would it happen that the developers have no internet connection? And how is it even possible to commit something without internet? But it's a nice feature though.
As I already stated: git commit is not exactly the same as svn commit. By doing "git commit" you commit your changes to your local repository. For this action you do not need an internet connection. In order to have those changes "publicly" available in the master repo, you have to do an additional "git push", which of course needs an internet connection
Vistaus wrote:2 SVN also supports that, but a little bit different than Git.
I'm not a SVN or Git expert, but from what I've "experienced" the big difference is:
Working with branches on SVN is slow:
When branching in SVN, you get a complete copy of the folder/repo you branched. This means double amount of space needed.
In Git working with branches is faster:
When branching in Git, the files are not copied to another location. They stay where they are, and somehow only the changed files are "copied" somewhere else (I don't know how exactly Git handles this, but it should be something like that)
Vistaus wrote:3 I don't think that is quite an advantage, because it doesn't take very much time to create an account on SVN imho. And also Git requires you to login sometimes, at least if you want a non-read-only copy of the branch.
When you give somebody a SVN account, you have to trust him, because once he has an account, he has access to all the files (I heard of ways to restrict this, but I don't know how hard/easy they are to configure)
In Git you only have acces to your own clone (and the master repo, if you have access to it), thus the barrier of people contributing can be lowered, as you don't need to have a full SVN account anymore.
About the logging in "issue":
Actually you have to enter a password/"login" on both SVN and Git if you want to access to the (remote) repository.
On Gitorious (where afaik KDE probably will move to) you need an SSH key which you have to enter everytime you push some changes to your remote repository.
With SVN you have to enter your Password.
Of course you can somehow configure Git/SVN to store that password, so that you don't have to enter it everytime