3 ms·
Comparing git with svn doesn't make sense. It's two different tools with different use-cases and a transition from svn to git only make sense for some (motivate
by gorm 16y ago
Comparing git with svn doesn't make sense. It's two different tools with different use-cases and a transition from svn to git only make sense for some (motivated) teams.
- wycats 16y agoWhile there are quite a few different workflows, there are a number of similar operations (get a repository, get updates from a remote, push changes to the remote). My point was not to compare git (as a whole) to subversion, it was to demonstrate how the tools handle those operations. I think it's reasonable for people who are moving from subversion to git to expect that commands for these operations will exist (and they, of course do). Finally, even in my limited description, I managed to demonstrate a benefit of git (namely, that the slightly different default workflow handles the common problem of rollback much more elegantly)
- j_baker 16y agoI think it can be useful to compare git and svn. True, it is comparing apples and oranges. However, that's a reasonable thing to do when you're considering migrating from apples to oranges.
- nfnaaron 16y agoWhat are the different use cases? I would have thought they're both basically version control, since one of the decisions in version control is whether to use svn or git or something else. So what use cases are svn appropriate for (and not git), and what use cases are git appropriate for (and not svn)?