sub-module support

Saravanan Shanmugham (sarvi) sarvi at cisco.com
Sun Oct 7 17:03:43 CDT 2007


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. 

Is there a reason why the forest extension Is not being considered for
standardization. That seems very similar to git sub-module and close
what we are looking for. Is there any possibility this feature could
become part of 1.0?

Sarvi  

     -----Original Message-----
     From: Matt Mackall [mailto:mpm at selenic.com] 
     Sent: Sunday, October 07, 2007 2:33 PM
     To: Saravanan Shanmugham (sarvi)
     Cc: mercurial at selenic.com
     Subject: Re: sub-module support
     Importance: High
     
     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.
     



More information about the Mercurial mailing list