3 ms·
Creating an svn repo was fast, yet you could not use it without a dedicated server, DNS configuration, security configuration, firewall configuration, etc. etc.
by PieterH 11y ago
Creating an svn repo was fast, yet you could not use it without a dedicated server, DNS configuration, security configuration, firewall configuration, etc. etc. If this was your only job, sure, a few hours' work. For the rest of us, begging a sysadmin or spending days learning the details.
Whereas with git it's literally "git init ." or clicking on Github.com and we're ready to roll.
I do appreciate the fact checking, and you're welcome to send me more comments. Errors of fact don't survive the editorial process, one hopes. Opinions, that's a different story.
- tom_mellior 11y ago> with git it's literally "git init ." That doesn't magically give you a shared, network-accessible repository with all the correct access controls. > or clicking on Github.com SourceForge has existed since 1999, and after a click you have always been ready to roll. > and you're welcome to send me more comments But I probably won't if your strategy is "spread misinformation first, then make others work to point out mistakes, then defend an indefensible position, then maybe change it". That's not how communities are built. That's what you yourself criticize in the section on merging strategies...