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

Re: Repositories stucture

From
Mateusz Loskot <mateusz@loskot.net>
Date
Apr 13, 2019, 15:23 UTC
Message-ID
<CABUeae9g-J3zXpkc1Y_6vQM5VQ0do3c9PT-300Vcvoxi5kQY1g@mail.gmail.com>
In-Reply-To
<5cl.5Cyq.1JuGDapDk}8.1SiN42@seznam.cz>
On Sat, 13 Apr 2019 at 07:32, Mgr Georg Black <georg.black@seznam.cz> wrote:
> People from big company(BC) wanna to have only one big repository with all code in it. BC wanna have to folders structure for language and projects. But for us is that idea bit uncomfortable because we rather have more repositories by language, maybe by project (in BC folders). It's useless for us that every developer on specific project and language have all other sources in their local repository. Is it the solvable?

Show the BC how Boost libraries structure the repositories with submodules There is single superproject https://github.com/boostorg/boost/ and large number of libraries (each with dedicated team of developers). Periodically, everything is synchronised into the superproject repo and prepared for release in single bundle.

Then, you may want to learn about submodule and subtree features of Git, and choose the one that suits best your workflow(s) to implement your repositories structure.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Previous: Mgr Georg Black
Message 2 of 2 in “Repositories stucture”
  1. Mgr Georg BlackApr 13, 2019
  2. Mateusz LoskotApr 13, 2019

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.