{"thread":{"id":"29060","subject":"workflow for component based design (newbie to Git)","startedAt":"2011-12-01T11:29:10Z","lastAt":"2011-12-01T12:53:19Z","messageCount":2,"participants":["Ivan Dimitrov","Frans Klaver"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"180197","messageId":"CAO8zR6N_kxQHA+Z=ruA5T8cc1A6km8Y3RouXib6oRXPWHzfA6A@mail.gmail.com","threadId":"29060","inReplyTo":null,"subject":"workflow for component based design (newbie to Git)","fromName":"Ivan Dimitrov","fromEmail":"ivand58@gmail.com","sentAt":"2011-12-01T11:29:10Z","receivedAt":"2011-12-01T11:29:10Z","isPatch":false,"sender":{"key":"ivand58@gmail.com","avatar":null},"body":"Hi all,\n\nPlease forgive me for asking this, but I can't seem to find\ninstructions anywhere.\n\nI'm planning to migrate from Serena PVCS to GIT, but I can't realize\nhow to assign a label only to particular files (component) and how to\napply the promotion model to my project with GIT ?\n\nSo, in general, how one can handle a project with component based\narchitecture (and workflow) with GIT?\n\nThanks in advance.\n"},{"id":"180198","messageId":"CAH6sp9NdJDsZJAfD0TX_rfi8_Uw66JxSczs6-sz6MSXu4S8hiw@mail.gmail.com","threadId":"29060","inReplyTo":"CAO8zR6N_kxQHA+Z=ruA5T8cc1A6km8Y3RouXib6oRXPWHzfA6A@mail.gmail.com","subject":"Re: workflow for component based design (newbie to Git)","fromName":"Frans Klaver","fromEmail":"fransklaver@gmail.com","sentAt":"2011-12-01T12:53:19Z","receivedAt":"2011-12-01T12:53:19Z","isPatch":false,"sender":{"key":"fransklaver@gmail.com","avatar":"https://avatars.githubusercontent.com/u/1876483?v=4"},"body":"On Thu, Dec 1, 2011 at 12:29 PM, Ivan Dimitrov <ivand58@gmail.com> wrote:\n\n> Please forgive me for asking this, but I can't seem to find\n> instructions anywhere.\n>\n> I'm planning to migrate from Serena PVCS to GIT, but I can't realize\n> how to assign a label only to particular files (component) and how to\n> apply the promotion model to my project with GIT ?\n>\n> So, in general, how one can handle a project with component based\n> architecture (and workflow) with GIT?\n\nIn general one would have one repository per component (typically a\nmodule). You can manage multiple repositories using git-submodule[1]\nor an alternative tool like it. Labels are then tags for that\nparticular submodule. Labeling single files is not something git is\ngoing to do, as it is tracking repository content rather than files.\n\nFrans\n\n[1] http://book.git-scm.com/5_submodules.html\n"}]}