Mercurial存储库架构(Mercurial repository architecture)

Mercurial存储库架构(Mercurial repository architecture)

我们有3个中央mercurial存储库，一个是稳定版本，它是上一版本中发布的代码，另外两个是dev存储库。

大部分时间我将在一个开发人员库上工作（但偶尔可能需要对其他开发人员库或稳定存储库进行更改）。

我是否在本地计算机上创建了三个目录并在每个目录中创建了一个mercurial存储库，或者是否有一种方法可以从我的计算机上的单个存储库中工作并将我的本地存储库与相应的中央存储库同步？

这里最好的方法是什么？

We have 3 central mercurial repositories, one is the stable version that is the code that went out in the last release, and the other two are dev repositories.

Most of the time I will be working on one of the dev repositories (but occasionally may have to make a change to the other dev repository or to the stable repository).

Do I create three directories on my local machine and create a mercurial repository in each, or is there a way in which I can work from a single repository on my machine and synchronise my local repository with the appropriate central one?

What's the best approach here?

最满意答案

3个目录是最好的方法。

您可以使用单个本地克隆，但是您将有相当多的工作，确保您不会将内容推送到您不应该使用的存储库。

拥有3个不同的本地文件夹可以更轻松地确保您在正确的文件夹中工作，并确保您不会意外地推送到生产/发布存储库。

3 directories is the best approach.

You can work with a single local clone, but you will have quite a bit of work ensuring you don't push things to a repository that you're not supposed to.

Having 3 distinct local folders makes it easier to ensure you're working in the right one, and ensure you're not accidentally pushing to the production/release repository.