Re: organizing multiple repositories with dependencies
- From
PJ Weisberg <pj@irregularexpressions.net>
- Date
- Apr 17, 2012, 22:25 UTC
- Message-ID
- <CAJsNXTmfRZvpO=ooB8yKUqGqbU4g5A78=dzt2vPPrs1q+J4ZrA@mail.gmail.com>
- In-Reply-To
- <CAE1pOi38krwXZuiYxtpLwm92N=NvWkP30V_=6cnHw=sdyk6QhA@mail.gmail.com>
On Tue, Apr 17, 2012 at 2:43 PM, Hilco Wijbenga <hilco.wijbenga@gmail.com> wrote:
Show 7 quoted lines
> I'm assuming that if you have subproject S in umbrella project U and a > branch "topic" in U then that same branch should exist in S. Any > changes in S's topic should show up in U's topic (probably after some > sort of update command like git fetch/pull). This should be unusual, > though, you should be working in U, not S. If you want to work on > something in S that you don't want to see in U, then you should not be > working in S's topic.
This paragraph makes me wonder why you want to use submodules at all. Wouldn't a sparse checkout be a better fit for what you're trying to accomplish?
-PJ
Gehm's Corollary to Clark's Law: Any technology distinguishable from magic is insufficiently advanced.