{"thread":{"id":"9695","subject":"New to git, related multi-projects","startedAt":"2007-08-29T18:18:14Z","lastAt":"2007-08-29T19:52:16Z","messageCount":2,"participants":["Jean-François Veillette","Alex Riesen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"51841","messageId":"7F6E024B-253E-40C6-9012-9CF1B2F374D8@yahoo.ca","threadId":"9695","inReplyTo":null,"subject":"New to git, related multi-projects","fromName":"Jean-François Veillette","fromEmail":"jean_francois_veillette@yahoo.ca","sentAt":"2007-08-29T18:18:14Z","receivedAt":"2007-08-29T18:18:14Z","isPatch":false,"sender":{"key":"jean_francois_veillette@yahoo.ca","avatar":null},"body":"Here is my setup, please briefly tell me what would be the suggested  \ngit configuration.\n\nThe company currently use cvs, it has a cvs tree where the first  \ndirectory level is per client, the second directory level is the  \nproject, then inside it we have the many artifacts, like :\ncvsserver/Shared/Documentation/PresentationTemplate.doc\ncvsserver/Shared/Documentation/AnalysisTemplate.doc\ncvsserver/Shared/Devel/CommonLib/*\ncvsserver/ClientA/ProjectA/Doc/Presentation.doc\ncvsserver/ClientA/ProjectA/Doc/Analysis.doc\ncvsserver/ClientA/ProjectA/Dev/ApplicationA/*\ncvsserver/ClientA/ProjectA/Dev/ApplicationB/*\ncvsserver/ClientA/ProjectA/Dev/ApplicationC/*\ncvsserver/ClientA/ProjectA/Dev/LibraryA/*\ncvsserver/ClientA/ProjectA/Dev/LibraryB/*\n\nWhat would be the best way to represent a similar setup in git ?\nI was thinking of having a repository at the project level, and add  \natomic  subdirectories (code for applications and libraries for  \nexample)  as submodules.\nIf submodule are the right way to go, can a submodule, include a  \nsubmodule, for example, ApplicationA use LibraryA and CommonLib ?\n\nThanks,\n\n- jfv\n"},{"id":"51846","messageId":"20070829195216.GB11824@steel.home","threadId":"9695","inReplyTo":"7F6E024B-253E-40C6-9012-9CF1B2F374D8@yahoo.ca","subject":"Re: New to git, related multi-projects","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-08-29T19:52:16Z","receivedAt":"2007-08-29T19:52:16Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Jean-François Veillette, Wed, Aug 29, 2007 20:18:14 +0200:\n> The company currently use cvs, it has a cvs tree where the first  \n> directory level is per client, the second directory level is the  \n> project, then inside it we have the many artifacts, like :\n> cvsserver/Shared/Documentation/PresentationTemplate.doc\n> cvsserver/Shared/Documentation/AnalysisTemplate.doc\n> cvsserver/Shared/Devel/CommonLib/*\n> cvsserver/ClientA/ProjectA/Doc/Presentation.doc\n> cvsserver/ClientA/ProjectA/Doc/Analysis.doc\n> cvsserver/ClientA/ProjectA/Dev/ApplicationA/*\n> cvsserver/ClientA/ProjectA/Dev/ApplicationB/*\n> cvsserver/ClientA/ProjectA/Dev/ApplicationC/*\n> cvsserver/ClientA/ProjectA/Dev/LibraryA/*\n> cvsserver/ClientA/ProjectA/Dev/LibraryB/*\n> \n> What would be the best way to represent a similar setup in git ?\n> I was thinking of having a repository at the project level, and add  \n> atomic  subdirectories (code for applications and libraries for  \n> example)  as submodules.\n> If submodule are the right way to go, ...\n\nnot necessarily. I'd try plain branches first, unless the client's\nprojects have lots of applications (or libraries, IOW, modules) and\nmany of them are optional for your development process. \"Optional\"\nbetter fits what submodules are: their presence is supermodule is\noptional too. Many fixes after introduction of the submodules was just\nignoring them :)\n\n> ... can a submodule, include a   submodule, for example,\n> ApplicationA use LibraryA and CommonLib ?\n\nyes.\n"}]}