From: Michael Treibton <mtreibton@googlemail.com>
To: git@vger.kernel.org
Subject: Submodules or separate repos?
Date: Mon, 25 Apr 2011 11:35:10 +0100 [thread overview]
Message-ID: <BANLkTinAC2Thuf_z_-DMEHotgF-tqpQYZw@mail.gmail.com> (raw)
hi,
please CC me as i am not subscribed
ive recently converted a project that was in svn to use git - and
that's gone well.
in doing this ive been wondering if i can't split up the respository
more. currently we have this:
project/
core/
modules/
moduleA/
moduleB/
Which i think is fairly typical of most projects.
i was wondering how feasible it would be to split out "moduleA" and
"moduleB" into their own repositories? to me that makes sense. but by
themselves neither "moduleA" or "moduleB" would compile without the
core.
So...
does this make more sense for submodules or separate repositories?
And if they were separate repositories, how would this work from a
development point of view? what about a release of the project? would
there be a makefile which pulled in a known version of tarball
released from each moduleX repository?
What do most other people do in this situation?
TIA!
Michael
next reply other threads:[~2011-04-25 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 10:35 Michael Treibton [this message]
2011-04-25 19:57 ` Submodules or separate repos? Jens Lehmann
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=BANLkTinAC2Thuf_z_-DMEHotgF-tqpQYZw@mail.gmail.com \
--to=mtreibton@googlemail.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;
as well as URLs for NNTP newsgroup(s).