GIT与Subversion的简单比较

最近买了本《version control with git》的动物书。给自己下了规定，一定要每天看一点。免得像之前的书一样，买了不怎么看，只是偶尔翻翻，有点浪费。目前看到DIFF这章。本章的结尾是比较了git 和 subversion的diff机制。于是想上网查一下具体git和subversion还有些什么比较大的区别。在GIT官方的WIKI上看到一下总结，简单翻译一下：

• Git is much faster than Subversion   GIT比 SVN快
• Subversion allows you to check out just a subtree of a repository; Git requires you to clone the entire repository (including history) and create a working copy that mirrors at least a subset of the items under version control.  SVN允许从服务器拿库中的某个子目录；GIT要求你clone整个库。
• Git’s repositories are much smaller than Subversions (for the Mozilla project, 30x smaller)  git库比subversion小。mozilla项目中小了30倍
• Git was designed to be fully distributed from the start, allowing each developer to have full local control  GIT完全基于分布式设计，开发人员具有代码库的完全控制。
• Git branches are simpler and less resource heavy than Subversion’s   git分支比subversion好用且省资源。
• Git branches carry their entire history  git分支带有完整历史记录
• Merging in Git does not require you to remember the revision you merged from (this benefit was obviated with the release of Subversion 1.5)
• Git provides better auditing of branch and merge events。 git提供更好的分支合并的检查。
• Git’s repo file formats are simple, so repair is easy and corruption is rare. git的repo文件系统简单，易于修复，也不容易损坏。
• Backing up Subversion repositories centrally is potentially simpler – since you can choose to distributed folders within a repo in git.
• Git repository clones act as full repository backups. git中clone就是整个库的备份
• Subversion’s UI is more mature than Git’s. svn的UI比git的UI成熟。
• Walking through versions is simpler in Subversion because it uses sequential revision numbers (1,2,3,..); Git uses unpredictable SHA-1 hashes. Walking backwards in Git is easy using the “^” syntax, but there is no easy way to walk forward. SVN的版本号人性化，git中使用SHA1作为commit标识。难懂。

 

总的来说GIT先进很多。但是也并非什么都比SVN好。其中我觉得它那SHA1的commit ID就很难用。在图形化的git中还好，但是命令行下要输入commit ID真是累。SVN使用上必须要建立一个服务器就很麻烦，这点远不如git来的轻量。也是我个人比较喜欢git的主要原因。或者说这也是分布式SCM的主要优点。