Hi, On Fri, 27 Jul 2007, Ray Lehtiniemi wrote: > On Friday 27 July 2007 13:05, Johannes Schindelin wrote: > > On Fri, 27 Jul 2007, CPD wrote: > > > > We produce variations based on a (mostly) common codebase. In CVS I set > > > up "environment" modules for each platform, then when you are working on > > > that platform, you simply check out the correct environment and build. > > > Only the needed code and tools are exposed in that environment (this is > > > important as clients must NOT see each other's code and most customers > > > have some customization). I do this by defining and renaming modules in > > > the CVSROOT modules file. > > > > I would use branches for that. A base branch with the common code, and > > the customisations in all the branches, which merge from the base branch. > > this would break down if there were client-specific modules in the base > branch, though... how could those be hidden from the other clients? Umm. Don't put the client-specific modules in the base branch, then? The base branch is the common code, the code that every client may look at. Nothing else. Maybe I did not get the whole picture... do you want your _clients_ to access your main repo with Git? Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
