sub-module support

[Matt Mackall]

On Sun, Oct 07, 2007 at 11:45:00AM -0700, Saravanan Shanmugham (sarvi) wrote:
>  
>  
> Hi,
>     We are considering moving to a DSCM within in our group, and would
> like to start with a few trial projects. If we find the model working,
> we will expand its usage.
>  
> The choices are obviously between GIT and Mercurial. Windows support is
> good on Mercurial. But the concept of versioning sub-modules seems to
> tilt in favour of GIT.
>  
> We expect our code base to be large but modular, in that we expect to
> version sub-components independently. That is we do not want to have to
> version our entire code base together. Sub components need to be shared
> amoungst multiple higher level modules and platforms. 
>  
> We could like to be able to checkout and develop submodules
> independently. While also in certain cases want to manage a collection
> of sub-modules as a platform or higher level module,  and be able to
> version them together as well.
>  
> Git has sub-modules as part of the core system now. 
>  
> Mercurial has Forest extension support, but that seems second tier i.e.
> not part of the standard. Plus a note on the page says its not working.
>  
> So, can anyone tell what the Mercurial story  is with respect to
> managing sub-projects/sub-modules in the code base.

I plan to make something much like Forest part of the core, but it
will be post-1.0.

-- 
Mathematics is the supreme nostalgia of our time.