每个项目一个存储库还是一个存储库中的多个项目？
我刚刚开始使用来自 TFS 2010 等的 Visualsvn（通常是 SVN）。对于存储库，这些应该在每个项目中使用，还是我可以将多个项目签入到存储库中？
谢谢
I have just started using visualsvn (SVN in general, rather) coming from TFS 2010 etc. With repositories, should these be used per project or could I check in a number of projects into a repository?
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
好吧，只要您为每个项目维护正确的结构（对我来说，带有主干/分支/标签的默认结构是最有用的），这更多是一个品味问题。
但要考虑的一个因素是您的项目是否彼此接近。不同的存储库可以单独管理，所以如果您没有连接项目 - 我宁愿选择不同的存储库。
另一方面，如果项目正在（或者将来可能）相互使用 - 它们是单个存储库的候选者，因为您可以轻松地创建外部并立即维护它们。
对于单个公司来说，拥有单个全局存储库可能是最好的想法，因为在单个存储库上设置备份/镜像/其他内容比在数百个小型存储库上设置备份/镜像/其他内容要容易得多。
对于家庭开发，我更喜欢单独的存储库，因为将来很容易与某人共享其中一个存储库 - 使用简单的 xcopy 或开放网络访问存储库。
Well, as long as you're maintaining correct structure for each project (default one with trunk/branches/tags is the most usable as for me) it is more a matter of taste.
One consideration though is if your projects are close to each other. Different repositories could be managed separately, so if you have not connected projects - I'd rather choose different repositories.
On the other hand, if projects are (or possibly could in the future) using each other - they are candidates for single repository as you could easily make externals and maintain them all at once.
For single company it is probably the best idea to have single global repository as it is much easier to setup backup/mirroring/whatever on single piece than on hundred of small repositories.
For home developing I'd prefer separate repositories because it is easy to share one of them with somebody in the future - with simple xcopy or with opening network access to repo.
根据我的经验，将所有项目保存在一个存储库中仍然是更好、更明智的做法。使用多个存储库，您最终将管理许多转储文件和不同的用户权限设置。大多数公司都没有足够的资源来拥有负责存储库管理和管理的 Subversion 管理员。如果您只有一个存储库，那么它是存储库的一次性设置和配置。如果出现新项目，您不需要 Subversion 专家来为您设置单独的 Subversion 存储库。开发人员应该已经知道如何为新项目设置新文件夹。
From my experience, it is still better and sane to keep all your projects in one repository. With multiple repositories, you will end up managing many dump files and different user permission settings. Most companies don't have the luxury of having a Subversion Administrator that looks after the administration and management of repositories. If you have only one repository, it's a one-time setup and configuration of your repository. If a new project comes along, you don't need a Subversion expert to setup a separate Subversion repository for you. The developers should know already how to setup new folders for the new project.