From: Mateusz Loskot <mateusz@loskot.net>
To: git@vger.kernel.org
Subject: Re: Repositories stucture
Date: Sat, 13 Apr 2019 17:23:45 +0200 [thread overview]
Message-ID: <CABUeae9g-J3zXpkc1Y_6vQM5VQ0do3c9PT-300Vcvoxi5kQY1g@mail.gmail.com> (raw)
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
prev parent reply other threads:[~2019-04-13 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 5:17 Repositories stucture Mgr Georg Black
2019-04-13 15:23 ` Mateusz Loskot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABUeae9g-J3zXpkc1Y_6vQM5VQ0do3c9PT-300Vcvoxi5kQY1g@mail.gmail.com \
--to=mateusz@loskot.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).