git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Frans Klaver <fransklaver@gmail.com>
Date
Dec 1, 2011, 12:53 UTC
Message-ID
<CAH6sp9NdJDsZJAfD0TX_rfi8_Uw66JxSczs6-sz6MSXu4S8hiw@mail.gmail.com>
In-Reply-To
<CAO8zR6N_kxQHA+Z=ruA5T8cc1A6km8Y3RouXib6oRXPWHzfA6A@mail.gmail.com>
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
Previous: Ivan Dimitrov
Message 2 of 2 in “workflow for component based design (newbie to Git)”
  1. Ivan DimitrovDec 1, 2011
  2. Frans KlaverDec 1, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.