git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Mgr Georg Black" <georg.black@seznam.cz>
To: <git@vger.kernel.org>
Subject: Repositories stucture
Date: Sat, 13 Apr 2019 07:17:54 +0200 (CEST)	[thread overview]
Message-ID: <5cl.5Cyq.1JuGDapDk}8.1SiN42@seznam.cz> (raw)

Hello everyone.
We 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.
So how's the situation. 
There 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.
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?
I looked into some ways but with nothing practical experience Could anyone give me some advice which way is the best and why.
Simplified: 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.
Thanks to all for any direction or link.
Georg Black



             reply	other threads:[~2019-04-13  5:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13  5:17 Mgr Georg Black [this message]
2019-04-13 15:23 ` Repositories stucture Mateusz Loskot

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='5cl.5Cyq.1JuGDapDk}8.1SiN42@seznam.cz' \
    --to=georg.black@seznam.cz \
    --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).