Re: organizing multiple repositories with dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Apr 17, 2012 at 2:43 PM, Hilco Wijbenga
<hilco.wijbenga@xxxxxxxxx> wrote:

> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]