6/8/2023 0 Comments Tortoisehg subrepository![]() To remove a subrepository from the parent repository, delete its Subrepo at the desired revision, test in the top-level repo, thenĬommit in the parent repository to record the new combination. Thus, updating subrepos is a manual process. This is soĭevelopers always get a consistent set of compatible code and With the changeset checked out in the top-level changeset. Instead, they are updated to the changeset that corresponds Subrepos do not automatically track the latest changeset of their ![]() ".hgsubstate" and bind it to the committed changeset. Subrepository is tracked and the next commit will record its state in Clone or checkout the external projects where you want it If ".hgsub" does not exist, create it and add it to the parent The ".hgsubstate" file should not be edited manually. Mercurial automatically record the nested repositories states when committing in the parent repository. They are defined in ".hgsubstate", which is placed in the root of working directory, and capture whatever information is required to restore the subrepositories to the state they were committed in a parent repository changeset. Repositories, you have to create and add it to the parent Note that ".hgsub" does not exist by default in Mercurial Where "path/to/nested" is the checkout location relatively to the Git and Subversion subrepos are also supported: Mercurial subrepositories are referenced like: They are defined in ".hgsub", which should be placed in the root of working directory, and tell where the subrepository checkouts come from. They can appear anywhere in the parent working directory. ![]() Subrepositories are made of three components: Mercurial currently supports Mercurial, Git, and Subversion Parent Mercurial repository, and make commands operate on them as a Subrepositories let you nest external repositories or projects into a
0 Comments
Leave a Reply. |