From: agent59624285 <agent59624285@spamcorptastic.com>
To: git@vger.kernel.org
Subject: Is Git Scalable?
Date: Mon, 9 Feb 2009 08:29:47 -0800 (PST) [thread overview]
Message-ID: <21916359.post@talk.nabble.com> (raw)
I'm thinking on use Git in my projects. But I have a doubt I couldn't resolve
in the Git Docs or Wiki.
My organization has really big projects that we split in sub-projects, like
this:
Big Project
\---> Project A
\---> Project B
\---> Project B1
\---> Project B2
\---> Project B3
\---> Project C
\---> Project C1
and so on...
Now it's possible to work in each "small" project independently (like "git
clone ProjectB3") or you can work with a big project inheriting its
sub-projects (like "git clone ProjectB" that automatically makes a "git
clone ProjectB1", "git clone ProjectB2" and "git clone ProjectB3", putting
each sub-project in the right place).
The question is: does Git support something like this?
--
View this message in context: http://www.nabble.com/Is-Git-Scalable--tp21916359p21916359.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2009-02-09 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:29 agent59624285 [this message]
2009-02-09 16:51 ` Is Git Scalable? Jon Loeliger
2009-02-09 17:54 ` Johannes Schindelin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21916359.post@talk.nabble.com \
--to=agent59624285@spamcorptastic.com \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox