>I can not think of any scenario where svn would be preferable over a distributed vcs such as git or mercurial.
After forgetting to push after commit and then dropping your laptop, you'll know.
What? The result would be exactly the same, right? You don't have your unpushed commit if your laptop is broken, neither with svn nor with git. The only difference is that you still can use your local git repository if your server burns down, but you can't do that with svn.
>The result would be exactly the same, right?
Nope, like regularfry rightly pointed out.
>The only difference is that you still can use your local git repository if your server burns down, but you can't do that with svn. Even then I can `svn relocate`.
Look, I am not defending SVN for software development, I am a happy git camper. But git for technical writing is simply the wrong tool for the wrong job.
Re:Why Microsoft Word must die
by regularfry on Sunday October 13, 2013 @09:44AM
(#6542558)
With SVN a commit is a push. You can't forget to push after you've committed.
No but when I used svn I committed way less frequently so it ended up to be the same thing. With git I forget to push with svn I forgot to commit.
Right. The last time i used subversion was about 7 years ago, so i forgot it. But it makes sense for centralized vc
Re:Why Microsoft Word must die
by CJefferson on Sunday October 13, 2013 @11:07AM
(#6542825)
The biggest advantage of svn over git for non-technical users is that you can never end up with commit that then conflicts with another submit (as submits all happen on the server).
I have had various beginner git users get very confused when dealing with conflicts -- I have got myself quite confused on occasion too.
I don't know the state of visual tools for git but tortoisehg for mercurial is quite easy to get started with.