Re: Repositories stucture

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 13 Apr 2019 at 07:32, Mgr Georg Black <georg.black@xxxxxxxxx> 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




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux