threads / discuss / 29060

workflow for component based design (newbie to Git)

Subject: workflow for component based design (newbie to Git)

## tl;dr

2 messages between Dec 1, 2011 and Dec 1, 2011.

replies: 1people: 2as markdown or json

Ivan Dimitrov· Dec 1, 2011, 11:29 UTC · lore
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· Dec 1, 2011, 12:53 UTC · re: Ivan Dimitrov · lore

Re: workflow for component based design (newbie to Git)

On Thu, Dec 1, 2011 at 12:29 PM, Ivan Dimitrov <ivand58@gmail.com> wrote:
Show 9 quoted lines
> 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

← back to recent threads