subrepos

I have read every question on Mercurial subrepositories that I could and still not sure how it works. We are using hgweb.cgi on IIS so we have http:// paths to all of our repos. Here is the basic layout: /Libraries - http://server/Libraries /Project1 - http://server/Project1 /Project1/LibrariesSubrepo - http://server/Project1/LibrariesSubrepo (clone of libraries) /Project2 - http://server/Project1 /Project2/LibrariesSubrepo - http://server/Project2/LibrariesSubrepo (clone of libraries) In the .hgsub files, I have the path setup as: LibrariesSubrepo = LibrariesSubrepo If I want to work on the

Currently, I'm moving from a legacy version control system and moving my group's project to mercurial. As one example of the kinds of code I'm moving, I have a 25+ project Visual Studio solution, containing several separate application areas that all depend on common code. Looking over Stack Overflow, the closest question I found was this one , but it merely mentioned version control. I'm looking for a bit further advice, on specific implementation techniques of using Mercurial to manage these dependencies. A simplified view of the dependencies look something like the following. (This is for

We've got in a corporate environment an svn repository structure which looks like this: root libs shared_lib1 shared_lib2 private_lib public_code private_code where public_code is an external repository which is open source and where people from outside the company have read-write-access. shared_lib1 and shared_lib2 are also external repositories shared with a different group of programmers from an other company. I'm the maintainer and can do basically whatever is technically best, the outside users will have to adapt. I'm now wondering what the best way is to move from this structure to a

Situation I have two .NET solutions ( Foo and Bar ) and a common library that contains ProjectA, ProjectB, and ProjectC. Foo and Bar reference one or more library projects, but the library projects are not located within the Foo and Bar Solution folders. Directory structure: -- My Documents* -- Development -- Libraries -- ProjectA -- ProjectB -- ProjectC -- Projects -- Foo -- Solution -- .hg -- .hgignore -- Foo { Project Folder } -- FooTests { Project Folder } -- Foo.sln { References ProjectA } -- Foo.suo -- Bar -- Solution -- .hg -- .hgignore -- Bar { Project Folder } -- BarTests { Project