SVN是一个repo和许多客户端。Git是一个有很多客户端回购的回购，每个客户端都有一个用户。它是去中心化的，人们可以在本地跟踪自己的编辑，而不必将内容推送到外部服务器。

SVN的设计更加集中，其中Git基于每个用户都有自己的Git回购，这些回购将更改推回到中央回购中。因此，Git为个人提供了更好的本地版本控制。

同时，你可以选择TortoiseGit, GitExtensions(如果你在github上托管你的“中央”git库，他们自己的客户端- github for Windows)。

如果您正在寻求摆脱SVN，那么您可能需要对Bazaar进行一些评估。它是具有这种分布式元素的下一代版本控制系统之一。它不像git那样依赖POSIX，所以有原生的Windows版本，它有一些强大的开源品牌支持。

但您甚至可能还不需要这些特性。看看分布式vcs的特点、优点和缺点。如果您需要的不仅仅是SVN提供的功能，请考虑使用一个。如果您不喜欢，您可能希望坚持使用SVN(目前)的高级桌面集成。

这可以归结为:

你的发展是线性的吗?如果是这样，您应该坚持使用Subversion。

另一方面，如果您的开发不是线性的，这意味着您将需要为不同的更改创建分支，然后将这些更改合并回主开发线(Git称为主分支)，那么Git将为您做更多的工作。

我会选择SVN，因为它传播更广泛，知名度更高。

我想Git更适合Linux用户。

我从来没有理解过“git在Windows上不好”这个概念;我只在Windows下开发，git从来没有遇到过任何问题。

我绝对推荐git而不是subversion;它只是更加通用，并且允许“离线开发”，这是subversion永远无法做到的。它可以在几乎所有可以想象到的平台上使用，并且拥有比你可能使用过的更多的功能。

在做了更多的研究，并查看了这个链接:https://git.wiki.kernel.org/articles/g/i/t/GitSvnComparison_cb82.html

(摘录如下):

It's incredibly fast. No other SCM that I have used has been able to keep up with it, and I've used a lot, including Subversion, Perforce, darcs, BitKeeper, ClearCase and CVS. It's fully distributed. The repository owner can't dictate how I work. I can create branches and commit changes while disconnected on my laptop, then later synchronize that with any number of other repositories. Synchronization can occur over many media. An SSH channel, over HTTP via WebDAV, by FTP, or by sending emails holding patches to be applied by the recipient of the message. A central repository isn't necessary, but can be used. Branches are even cheaper than they are in Subversion. Creating a branch is as simple as writing a 41 byte file to disk. Deleting a branch is as simple as deleting that file. Unlike Subversion branches carry along their complete history. without having to perform a strange copy and walk through the copy. When using Subversion I always found it awkward to look at the history of a file on branch that occurred before the branch was created. from #git: spearce: I don't understand one thing about SVN in the page. I made a branch i SVN and browsing the history showed the whole history a file in the branch Branch merging is simpler and more automatic in Git. In Subversion you need to remember what was the last revision you merged from so you can generate the correct merge command. Git does this automatically, and always does it right. Which means there's less chance of making a mistake when merging two branches together. Branch merges are recorded as part of the proper history of the repository. If I merge two branches together, or if I merge a branch back into the trunk it came from, that merge operation is recorded as part of the repostory history as having been performed by me, and when. It's hard to dispute who performed the merge when it's right there in the log. Creating a repository is a trivial operation: mkdir foo; cd foo; git init That's it. Which means I create a Git repository for everything these days. I tend to use one repository per class. Most of those repositories are under 1 MB in disk as they only store lecture notes, homework assignments, and my LaTeX answers. The repository's internal file formats are incredible simple. This means repair is very easy to do, but even better because it's so simple its very hard to get corrupted. I don't think anyone has ever had a Git repository get corrupted. I've seen Subversion with fsfs corrupt itself. And I've seen Berkley DB corrupt itself too many times to trust my code to the bdb backend of Subversion. Git's file format is very good at compressing data, despite it's a very simple format. The Mozilla project's CVS repository is about 3 GB; it's about 12 GB in Subversion's fsfs format. In Git it's around 300 MB.

在阅读了所有这些之后，我确信Git是可行的方法(尽管存在一点学习曲线)。我也在Windows平台上使用过Git和SVN。

我很想听听其他人在读完上面的文章后会怎么说?

Git在Windows下还不受本地支持。它针对Posix系统进行了优化。然而，运行Cygwin或MinGW可以让你成功运行Git。

现在我更喜欢Git而不是SVN，但是如果你来自CVS, SVN的土地，它需要一段时间才能超过阈值。