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

How to organize multiple small reusable components with Git?

From
BTBing Tian <tianbing1212@gmail.com>
Date
Jul 23, 2015, 11:20 UTC
Message-ID
<CAMDZmAEf4afqhR4WT4e-dXjY5OWUSoE_WVGj1ztW-pA=ym9e3A@mail.gmail.com>
I am using git to manage some circuit components.
Each component is small and I plan to create a "component" project in
Git to hold all the small components.
Each component may have several released version, such as
Comonent1_V1, Component1_V2, Comonent2_V1, Component2_V2.
And for future reuse, I may use Component1_V1+Component2_V2, or
Component1_V2+Component2_V1 in my local directory.
So, I plan to create several directories, each for one version of one
component. I looks like followings:
Components
     |------Component1
     |                 |------------------Version1(Dir)
     |                 |------------------Version2(Dir)
     |-------Component2
                       |------------------Version1(Dir)
                       |------------------Version2(Dir)

I want to know, is the above a suitable way in Git? Are there some risks for my project and Git? Any suggestions to cover this case in Git?

Next: Adam Kurkiewicz
Message 1 of 3 in “How to organize multiple small reusable components with Git?”
  1. Bing TianJul 23, 2015
  2. Adam KurkiewiczJul 23, 2015
  3. Adam KurkiewiczJul 25, 2015

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.