你已经从颠覆转向善变了吗？值得付出努力吗？
我正在更好地了解 Mercurial 版本控制系统，并且正在考虑从 SVN 进行转换。
有人已经转换了吗？对于您和您的团队来说，转变是否困难？ 您能否给出一些建议，是继续使用 SVN 还是选择 Mercurial？
I am in the process of knowing Mercurial versioning system better, and I am considering convert from SVN.
Anyone already converted? Was that difficult for you and your team to switch?
Can you give any advice to stay with SVN or go for Mercurial?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我转换了。起初只是为了尝试一下，但我已经成为了它的忠实粉丝。我实际上并没有转换我的个人存储库，我只是导出最新的并将文件添加到新的 Mercurial 存储库。
一些基本的 hg 命令与 svn 中的命令类似，因此应该可以帮助您开始熟悉。 这里是对 Joel 差异的解释。
重要的是，要对使用 hg 新流程持开放态度。它允许更多的分支和快速提交，如果您使用突破颠覆心态，您将充分利用 hg。
I converted. At first it was just to try it out but I have become a big fan. I didn't actually convert my personal repositories, I just exported the latest and added the files to a new Mercurial repository.
Some of the basic hg commands are similar to those in svn so that should help you start getting comfortable. Here is an explanation of the differences from Joel.
Importantly, be open to using a new process with hg. It allows much more branching and quick committing, you'll get the most out of hg if you use break out of the subversion mindset.
一旦开始，你就永远不想回去。优势是巨大的。
我故意避免在 SVN 下进行分支，因为每次合并都需要数小时的调整。现在，我期待着分支，因为它效果很好。它使开发新功能变得更加容易。
此外，离线工作的能力非常棒。
这篇SO文章介绍了转换详细过程（非常简单）。您将能够保留您的历史记录，同时受益于 DVCS。
这个SO问题详细介绍了DVCS的好处，所以我我们会提到 Mercurial 的一个特定优势。如果您使用像 TortoiseSvn 这样的 GUI，您将会对 TortoiseHg。该应用程序不断改进，可以轻松查看待处理的更改和历史更改。花了一段时间才达到这种质量水平，但现在，我讨厌使用 TortoiseSvn，因为在审查待处理的更改和决定要提交的内容时，它的性能更差。
Once you start, you'll never want to go back. The advantages are huge.
I intentionally avoided branching under SVN, because every merge required hours of tweaking. Now, I look forward to branching because it works so well. It has made developing new features so much easier.
Furthermore, the ability to work offline is fantastic.
This SO article covers the conversion process in detail (its quite simple). You'll be able to preserve your history, but benefit from a DVCS.
This SO Question deals with DVCS benefits in detail, so I'll mention a Mercurial specific advantage. If you use a GUI like TortoiseSvn, you'll be pleasantly surprised by TortoiseHg. This app is continually improved and makes it very easy to view your pending changes and historical changes. It took a while to get to this level of quality, but now, I hate using TortoiseSvn, because it is just worse when it comes to reviewing pending changes and deciding what you want to commit.
我没有使用 Mercurial 的经验（使用 git 代替），但是像 Mercurial 或 git 这样的优秀 DVCS 与 svn 之间的经验差异是一旦你完成了学习曲线就无法回头的事情。
我最近的一份工作涉及在使用 git 一两年后重新使用集中式 svn 存储库。我通过使用 git-svn 桥来接近它，发现与 svn 相比，我对提交有很好的控制，并且可以使提交和分支静置、翻转和装死，这给了我比我的方法更有用的优势。 svn 使用同事，此外，由于进行本地提交的非常细化和频繁的性质，我进行了比较大量的提交。这是一个很大的好处。
我真的非常建议给自己一些时间来进行 DVCS。
I don't have experience with mercurial (use git instead) but the difference in experience between a good DVCS like mercurial or git vs. svn is something that you truly can't go back from once you've gotten past the learning curve.
I had a job recently that involved going back to using a centralized svn repository after using git for a year or two. I approached it by using the git-svn bridge, and found that I had great control over the commits compared to svn, and could make the commits and branches sit, roll over, and play dead in ways that gave me a useful advantage over my svn using co-workers, in addition to the large volume of commits that I made by comparison because of the very granular and frequent nature of doing local commits. It was a great benefit.
I really really recommend giving yourself some time with a DVCS.