sub-module support

[Saravanan Shanmugham (sarvi)]

The code base will be large with many components, potentially in the
lower 100s. 
A subset of these components would then need to be combined together to
build specific higher level components or products. These higher level
components or products might use specific versions of these
sub-components.

So, it might not make sense to have all of them as one respository. And
having them all as separate repositories, would mean we need to manage
specific sets/collections of these repositories, be able to version that
set/collection, and so on.

So the Hg Forest and the Git sub-modules make sense to us.

Sarvi 

     -----Original Message-----
     From: John D. Mitchell [mailto:jdmitchell at gmail.com] 
     Sent: Sunday, October 07, 2007 3:19 PM
     To: Saravanan Shanmugham (sarvi)
     Cc: Matt Mackall; mercurial at selenic.com
     Subject: Re: sub-module support
     Importance: High
     
     Good afternoon,
     
     On 10/7/07, Saravanan Shanmugham (sarvi) <sarvi at cisco.com> wrote:
     [...]
     > The code base is quite large and not being able to work 
     with it in a 
     > modular fashion, would mostly likely be a deal breaker 
     for us. Atleast 
     > for immediate adoption.
     
     Just curious but... What, precisely, do you need to be 
     able to do that you can do by have each of your "modules" 
     in a separate repository?
     
     I.e., if you already expect to evolve the modules 
     independently then what capability are you worried about 
     (not) having?
     
     Thanks,
     John