Mercurial和SVN并排在同一工作目录中? [英] Mercurial and SVN side by side in same working directory?

问题描述

我们的环境当前使用SVN.我想更频繁地提交，但是我不想破坏任何主要分支.我个人比SVN更喜欢汞.如果我在SVN工作副本中初始化存储库，如果我只是定期提交到Mercurial存储库并将工作修订提交到SVN分支，会出现任何问题吗?

Our environment currently uses SVN. I would like to commit alot more often, but I don't want to break any of the main branches. Personally I love mercurial much much more than SVN. If I hg init a repository in my SVN working copy would any issues arise if I just commit into the mercurial repository on a regular basis and committed working revisions into the SVN branch?

我们当前的环境尚未设置，因此每个开发人员都拥有自己的SVN分支，因此这不是可行的解决方案.

Our environment is not currently setup such that each developer has their own SVN branch, and so this is not a viable solution currently.

推荐答案

让Mercurial和Subversion共享工作文件夹不会有任何问题. Subversion将其文件保存在.svn文件夹中，而Mercurial将其文件保存在顶层的.hg文件夹中.

There will not be any problem with having Mercurial and Subversion share a working folder. Subversion keeps its files in .svn folders while Mercurial keeps its files in a .hg folder at the top level.

为方便起见，您可以考虑在.hgignore文件中添加.svn/条目，以免意外提交Mercurial存储库中的.svn文件夹.

For convenience, you may consider adding a .svn/ entry to your .hgignore file so you don't accidentally commit .svn folders in your Mercurial repository.

话虽如此.您不必完全使用Subversion. Mercurial可以与Subversion交互，而无需Subversion客户端.请参见使用Subversion .

That being said. You do not necessarily need to use Subversion at all. Mercurial can interface with Subversion without a subversion client. See Working with Subversion.

这篇关于Mercurial和SVN并排在同一工作目录中?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！