# workflow for component based design (newbie to Git) 2 messages from 2011-12-01 to 2011-12-01. Participants: Ivan Dimitrov, Frans Klaver. Thread: https://gitlist.dev/t/29060 ## Ivan Dimitrov, 2011-12-01 11:29 Subject: workflow for component based design (newbie to Git) Message-ID: URL: https://gitlist.dev/e/CAO8zR6N_kxQHA%2BZ%3DruA5T8cc1A6km8Y3RouXib6oRXPWHzfA6A%40mail.gmail.com ``` Hi all, Please forgive me for asking this, but I can't seem to find instructions anywhere. I'm planning to migrate from Serena PVCS to GIT, but I can't realize how to assign a label only to particular files (component) and how to apply the promotion model to my project with GIT ? So, in general, how one can handle a project with component based architecture (and workflow) with GIT? Thanks in advance. ``` ## Frans Klaver, 2011-12-01 12:53 Subject: Re: workflow for component based design (newbie to Git) Message-ID: URL: https://gitlist.dev/e/CAH6sp9NdJDsZJAfD0TX_rfi8_Uw66JxSczs6-sz6MSXu4S8hiw%40mail.gmail.com In-Reply-To: ``` On Thu, Dec 1, 2011 at 12:29 PM, Ivan Dimitrov wrote: > Please forgive me for asking this, but I can't seem to find > instructions anywhere. > > I'm planning to migrate from Serena PVCS to GIT, but I can't realize > how to assign a label only to particular files (component) and how to > apply the promotion model to my project with GIT ? > > So, in general, how one can handle a project with component based > architecture (and workflow) with GIT? In general one would have one repository per component (typically a module). You can manage multiple repositories using git-submodule[1] or an alternative tool like it. Labels are then tags for that particular submodule. Labeling single files is not something git is going to do, as it is tracking repository content rather than files. Frans [1] http://book.git-scm.com/5_submodules.html ```