Subject: Re: Sharing nested subparts of large repository?

From: LordSmoke <[email-masked]>
Date: Thu, 5 Apr 2012 01:32:34 -0700 (PDT)

Okay, it seems submodules really were the answer. I split my app into a
standalone public subtree and a development subtree that will use the public
source as a submodule (haven't actually done that yet, though). These will
be excluded from the parent git repository, but I guess that is fine since
the parent is used mainly for archiving and the remote repository serves as
the code archive.

--
View this message in context: http://git.661346.n2.nabble.com/Sharing-nested-subparts-of-large-repository-tp7403743p7439149.html
Sent from the git mailing list archive at Nabble.com.