学习版本控制首先使用 git 还是通过 SVN？
目前我所在的一个小组使用 SVN。我们正在考虑迁移到 git。我个人使用过 git（并且实际上使用 git-svn 桥接回主 SVN 存储库），所以我确信它的好处。
一个问题是 git 比 SVN 更复杂。我们有一些全新的人员需要从头开始学习版本控制。有人有直接跳进 git 来教授版本控制的经验吗？我想知道这是否会太多，或者是否可能更容易不必忘记基于 SVN 的期望。
有没有人有这两种方法的经验 - 直接跳到 git，或者先熟悉 svn？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
使用你将要使用的东西。没有理由浪费时间去养成不适合您的生产环境的习惯。源头控制不是脑外科手术——不要让它变得比原来更难。
Use what you're going to use. There's no reason to waste time picking up habits that aren't applicable to your production environment. Source control isn't brain surgery - don't make it harder than it has to be.
我认为这可能取决于用户的数量和你拥有的设置，对于没有太多分支或特殊功能的小用户群来说学习 Git 实际上非常简单，并且源代码控制的核心概念是相同的。当您获得具有多个分支机构和开发人员的更复杂的项目管理策略时，情况就开始出现分歧。
所以，如果你有一个小团队，我会建议直接跳入 Git。
如果您有一个更大的团队并且直接跳入 Git，那么一旦您更好地了解了系统，您可能需要重新配置如何设置存储库。
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.
git 的学习曲线简直就是地狱。学习一点点很容易，但也很危险:-)
然而，从很多方面来说，它是一个很好的工具，而且我认为首先学习 svn 不会为您的用户带来很好的服务。 git 的许多优点（分支和合并、克隆、断开连接的提交）在 svn 上下文中没有意义，或者它们的工作方式不同。
以下是我在教人们 git 时告诉人们的一些事情：
The learning curve for git is pure hell. A little learning is easy, but is also dangerous :-)
However, in many ways it is a nice tool, and I don't think your users will be well served by learning svn first. Many of the strengths of git (branching and merging, cloning, disconnected commits) don't make sense in a svn context, or they work differently.
Here are some of the things I tell people when I'm teaching them git:
git-gui:-)我不知道哪个更好，但是 git 暴露了一些关于源代码控制的“更高层次”的思考，我希望我知道这些，即使我只知道 svn...
如果你能处理学习曲线，我推荐 git。
I don't know which is better, but git exposes some 'higher level' thinking about source control that I wish I had known even when all I knew about was svn...
If you can handle the learning curve, I'd recommend git.
我处于类似的位置：使用 git-svn 而其他人使用普通 svn。对我们来说，不同之处在于我们从 VSS 转向了 SVN。尝试教人们有关原子提交的知识已经够困难的了，我认为我们不会尝试强制使用 git。
如果你有新人，我会直接使用 git，因为当你有本地提交和
I'm in a similar position: using git-svn while others use plain svn. The difference for us is we came off of VSS to SVN. Trying to teach people about atomic commits was hard enough, I don't think we'll ever try forcing git.
If you have fresh people I'd go for straight git because version control is so much more compelling when you have local commits and