Pavel Lyalyakin

Greenhorn
+ Follow
since Jan 02, 2016
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Pavel Lyalyakin

Rick Umali wrote:I reviewed the Git/SVN comparison page on the Git Wiki:

https://git.wiki.kernel.org/index.php/GitSvnComparison

The author, Shawn Pearce, points out some advantages SVN has over Git:

1) You can retrieve parts of an SVN repository. With Git, you cannot obtain "part" of a repository (though you can clone up to a certain depth).

2) SVN has predictable revision numbers. Git, on the other hand, has SHA1 IDs for its commit IDs.

A small list, to be sure. I hope others chime in with more.



Let me redress an injustice. According to http://svnvsgit.com/, the wiki page you refer to is ve-ery wrong on some (or even most of) the points about Git and SVN. It just rephrases some private email thread and does not provide fair comparison.

However, I can agree with the points you've mentioned: partial subtree checkouts in SVN, predictable revision numbers. But at the same time SVN has more pros. Just some of them:
  • Subversion has native support for storing large binaries and very huge repositories. Git does not have this by design.
  • Subversion has locking (i.e. it supports lock-modify-unlock workflow that is sometimes really helpful for non-mergeable items.
  • Subversion will never lose or forget your file's history. By design, Git does not track copies or renames at all. So it can lose file's history after copy and rename (and some other) operations!
  • Subversion is simple and straightforward.