4 ms·

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 differe

by phaer 13y ago

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.

regularfry 13y ago
With SVN a commit is a push. You can't forget to push after you've committed.
- jeltz 13y ago
  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.
- phaer 13y ago
  Right. The last time i used subversion was about 7 years ago, so i forgot it. But it makes sense for centralized vc
iSnow 13y ago
>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.