{"thread":{"id":"50930","subject":"Repositories stucture","startedAt":"2019-04-13T05:32:49Z","lastAt":"2019-04-13T15:24:14Z","messageCount":2,"participants":["Mgr Georg Black","Mateusz Loskot"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"373776","messageId":"5cl.5Cyq.1JuGDapDk}8.1SiN42@seznam.cz","threadId":"50930","inReplyTo":null,"subject":"Repositories stucture","fromName":"Mgr Georg Black","fromEmail":"georg.black@seznam.cz","sentAt":"2019-04-13T05:17:54Z","receivedAt":"2019-04-13T05:32:49Z","isPatch":false,"sender":{"key":"georg.black@seznam.cz","avatar":null},"body":"Hello everyone.\nWe are starting knowing and working with Git. We already used some version control  systems for parts of our work and for now we wanna to have one.\nSo how's the situation. \nThere is one big company with integration center and a few smaller firms which send their work there. We are developing in many languages on more projects.\nPeople 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?\nI looked into some ways but with nothing practical experience Could anyone give me some advice which way is the best and why. \nSimplified: we want to have many repositories in our firm so every developer could work with its repository with its language. Somewhere would be one repository for integration man who combine all smaller repositories in folders big repository for sending to BC. And this all have to work both ways. So we wanna donwnload changes from BC and copy them to our divides repos. So some folder to repo.\nThanks to all for any direction or link.\nGeorg Black\n\n\n"},{"id":"373798","messageId":"CABUeae9g-J3zXpkc1Y_6vQM5VQ0do3c9PT-300Vcvoxi5kQY1g@mail.gmail.com","threadId":"50930","inReplyTo":"5cl.5Cyq.1JuGDapDk}8.1SiN42@seznam.cz","subject":"Re: Repositories stucture","fromName":"Mateusz Loskot","fromEmail":"mateusz@loskot.net","sentAt":"2019-04-13T15:23:45Z","receivedAt":"2019-04-13T15:24:14Z","isPatch":false,"sender":{"key":"mateusz@loskot.net","avatar":"https://gravatar.com/avatar/fe5a0ce8995d4986f5c46aad6353e21717808da58e4bc710da1a100e247be239?d=mp&s=160"},"body":"On Sat, 13 Apr 2019 at 07:32, Mgr Georg Black <georg.black@seznam.cz> wrote:\n> 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?\n\nShow the BC how Boost libraries structure the repositories with submodules\nThere is single superproject https://github.com/boostorg/boost/\nand large number of libraries (each with dedicated team of developers).\nPeriodically, everything is synchronised into the superproject repo\nand prepared for release in single bundle.\n\nThen, you may want to learn about submodule and subtree features of Git,\nand choose the one that suits best your workflow(s) to implement your\nrepositories structure.\n\nBest regards,\n-- \nMateusz Loskot, http://mateusz.loskot.net\n"}]}