当我们有许多共享源文件的项目时，Mercurial 是一个不错的选择吗
其范围是我们有三个主要项目。一些源文件在项目之间共享。 20 年来，有近 300 万行代码（不包括注释或空格）。我们目前使用 Source Safe 进行版本跟踪。但这开始让我们失望，因为我们不仅扩展了我们的产品，而且还扩展了我们在共享的不同模块中玩的开发人员数量。共享文件的一个示例是模板类。代码很扎实，在很多项目中都有使用。它是单个文件，因此仅在项目之间共享。现在 20 年后，一个文件已增长到超过 1000 个文件（是的，我很想重构并创建库，但没有发生）。 Mercurial 是否以某种方式支持相同类型的概念？
谢谢 标记
The scope of this is that we have three main projects. Some of the source files are shared between the projects. There are nearly 3 million lines of code (not including comments or spaces) that has grown over 20 years. We currently use Source Safe for our version tracking. But this is starting to fail us as we expand not only our products but also by how many developers we have playing in different modules that are shared. An example of a shared file would be a template class. The code is solid and is used in many projects. It is a single file so it is just shared between the projects. Now 20 years later that one file has grown to over 1000 files (Yes I would love to refactor and make libraries, not happening). Does Mercurial support the same kind of concept in some way?
Thanks
Mark
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果我正确地阅读了您的问题，Mercurial subrepos 可能就是您正在寻找的。
Mercurial subrepos may be what you're looking for, if I'm reading your question correctly.