subrepos

RyanWilcox had posted a script at here , that can use the following command to add subrepository automatically: $ cd $TOP_OF_HG_PROJECT $ addsubrepo.sh $URL_TO_HG_PROJECT relative_path/you/want_to/put_the_subrepo How to translate it into Windows batch or powershell script? Here is a quick and dirty translation. Haven't tested as I got no Mercury around. The initial script seems to be easy enough to translate into Powershell. # Project and relative paths as script parameters param([string]$project, [string]$relPath) # Let's see if there is an item .hg. If not, report error and quit if((test

I often work with Mercurial by keeping a local store of my upstream clones, and then just cloning again locally for my actual working environment: $ cd /clones $ hg clone ssh://external-repo.example.com/some/repo/path/foo $ cd ~/Development $ hg clone /clones/foo This is particularly useful for me because I often want to make new clones on airplanes, etc., where I have no internet access. However, this doesn't work when the original clone contains subrepos - the presence of the .hgsubstate file means that hg will always go out to the internet instead of grabbing the local cloned revision (even

I've been reading about subrepositories and how to extract an existing folder from a Mercurial repository to a subrepository using the convert extension and a filemap. I can successfully do this. If I have the following folder structure: C:\Project ---Project\root.txt ---Project\SubFolder ---Project\SubFolder\fileinsubfolder.txt I can make a subrepository of SubFolder. In much the same way I can extract everything else a seperate repositorie (in this example the second repository would just have the root.txt file). Afterwards I can add the SubFolder repository as a subrepository to the second

Is it possible to create a mercurial repository inside an existing mercurial repository? The idea is to handle subdirectories of a repository as different repositories, how do you do that? I'm not talking about subrepos (at least, if I understood the purpose of subrepos...), but if this is how subrepos do exist for, I got it wrong and I'll try to get it right :) Thanks ~Aki EDIT: To be more clear, I'd like to know what happens, the practices and the implications of having a repository inside another one, without specifying modules/subrepos. In other words: what happens if I just do: hg init

I'm struggling on how to correctly track nested repositories using TortoiseHg. I have a main repository that tracks my whole project. This project contains several little plugins that are stored inside a plugins/ subdirectory. I would love to track each plugin independently (committing and pushing to BitBucket for each one of them) while still being able to make a "whole" commit of my project, including the changes made to the plugins and pushing it to an other location (not BitBucket). What I've done so far is creating a new repo for each of my plugins. I can commit and push them to BitBucket

I'd like to evaluate Mercurial for my working projects. But most of my projects very heavily rely on the presence of svn:externals-like support. I've searched over StackOverflow and googled for corresponding support in Mercurial. All I found is subrepo feature added in Mercurial 1.3, but the page for this feature said: subrepos are an experimental feature for Mercurial 1.3. So don't do this on mission critical repositories! I don't want to use something unstable. Can anybody shed some light on the real status of this feature, and the plans of polishing/finishing it and when it will be called

There have been a couple of questions about Hg sub-repo dependencies in the past ( here and here ) but the accepted answers don't seem to address the problem for me. A project of mine has 4 dependencies: A, B, C, D. D is dependent on A, B and C; and B and C are dependent on A: I want to use Hg sub-repositories to store them so I can track what version of each they rely on. This is because, while I am using A,B,C and D in this project, other projects will require just A and B . Therefore B and C must track what version of A they need independently of D. At the same time, in my application the