学习使用git的版本控制或通过SVN？

本文介绍了学习使用git的版本控制或通过SVN？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 目前，我是使用SVN的一部分。我们正在考虑转向git。我个人使用过git（并且实际上是使用git-svn桥接到主要的SVN存储库），所以我相信它的好处。

一个问题是git比SVN复杂。我们有一些从一开始就需要学习版本控制的全新人物。有没有人有直接跳入git来教授版本控制的经验？我想知道它是否会太多，或者如果它可能更容易没有了解SVN的期望。

有没有人有过任何一种方法的经验 - 直接跳入git，或先熟悉svn？

因此，如果你有一个小团队，我会说跳直入Git。

如果你有一个更大的团队，并且直接跳入Git，那么准备好意识到你可能需要重新配置一旦你理解了以后你如何设置你的仓库该系统更好。

Currently a group I am a part of uses SVN. We are looking at moving to git. I have used git personally (and am actually using git-svn to bridge back to the main SVN repository), so I am convinced of its benefits.

One concern is that git is more complex than SVN. We have some brand new folk who will need to learn version control from the beginning. Does anyone have any experience teaching version control by jumping straight into git? I am wondering if it would be just too much or if it might be easier not having to unlearn SVN based expectations.

Does anyone have any experience of either approach - jump straight into git, or get familiar with svn first?

解决方案

I think it might depend on the number of users and the setup you have, learning Git for a small user base without too many branches or special features is actually very simple and the core concepts of source control are the same. Where it starts to diverge is when you get a more complex project management strategy with multiple branches and development staff.

So, if you have a small team, I would say jump straight into Git.

If you have a larger team and you jump straight into Git then be prepared to realize you might need to reconfigure how you have setup your repositories at a later date once you understand the system better.