Nested repos

[John Patterson]

Hi,

I am using hg hg 1.2.1 which is the current macports package. I have a
number of code modules shared between several larger projects.  Each has its
own repo and so do the larger projects that use these modules.  I want each
larger project to have its own version of the modules so that as releases
are made they always include the correct state of the modules.  I also don't
want to break other projects using the modules or be forced to modify them
when the shared versions change.

/ModuleA
/ModuleB
/LargeProject1
/LargeProject1/ModuleA
/LargeProject1/ModuleB
/LargeProject2
/LargeProject2/ModuleA
/LargeProject2/ModuleB

I expected this to work without the new subrepos feature because when I
commit a large project I do not want any special handling of the included
modules.  They should also be included in the large projects repository. 
However what I have found is that code in /LargeProject1/ModuleB is not
included when I issue a hg status.

Is there some way around this?

Thanks,

JD


-- 
View this message in context: http://www.nabble.com/Nested-repos-tp24530557p24530557.html
Sent from the Mercurial mailing list archive at Nabble.com.