在 Mercurial 中使用子存储库来“共享代码”
我有一个存储库，其中包含三个子文件夹。
A、B 和一个核心文件夹。
我需要 A 和 B 中 core 文件夹的文件。因此 core 文件夹的每个文件都应该位于 A 和 B 中的另一个文件夹中，并且对文件的每次更新都应该提交到“core”，反之亦然。
所以我尝试将 core 文件夹创建为子存储库并将其添加到 A 和 B。
例如，在文件夹 B 中，.hgsub www = ../core
中有以下行 在主存储库中位于 .hgsub core = core
我认为我做错了什么，但也许你有一个提示如何实现我想要的:)
（更新）
澄清一下：
该存储库包含应用程序的不同“项目”。
A 为 Android，B 为 iOS。 “核心”包含 HTML+JS 文件，稍后在 Android 和 iOS 项目中使用这些文件来构建带有 PhoneGap 的应用程序。
I have a repository in which I have three subfolders.
A, B and a core folder.
I need the files of the core folder in A and in B. So every file of the core folder should be inside another folder in A and B and every update to the files should be commited to "core" and vice versa.
So I tried to make the core folder to a subrepository and add this to A and B.
So in folder B for example there is following line in the .hgsub www = ../core
In the main repository is in the .hgsub core = core
I assume there is something I do wrong, but maybe you have a hint how to achieve what I want :)
(Update)
To clarify:
The repository contains different "projects" for an app.
A is Android and B is iOS. The "core" contains HTML+JS files which are later used in the Android and iOS projects to build apps with phonegap.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果我理解正确的话，你就会明白：
repo | +-- core <--+ +-- A | +-- core ---+ \A\core and \B\core should be equal to \core +-- B | +-- core ---+Mercurial 中没有任何东西可以帮助你解决这个问题。
您可以做的是：
core-repo +-- (content) repo +-- A +-- core --- sub-repo pointing to core-repo +-- B +-- core --- sub-repo pointing to core-repo这将允许您将更改提交到 A 内的子存储库，推送，然后拉取并更新到 B 内的子存储库，使它们保持同步。
If I understand you right, you have this:
repo | +-- core <--+ +-- A | +-- core ---+ \A\core and \B\core should be equal to \core +-- B | +-- core ---+There is nothing in Mercurial that will help you with this.
What you can do is this:
core-repo +-- (content) repo +-- A +-- core --- sub-repo pointing to core-repo +-- B +-- core --- sub-repo pointing to core-repoThis will allow you to commit changes to the sub-repo inside A, push, and then pull and update into the sub-repo inside B, keeping them in sync.