Re: organizing multiple repositories with dependencies

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

 



On Tue, Apr 24, 2012 at 11:54 AM, Hilco Wijbenga
<hilco.wijbenga@xxxxxxxxx> wrote:
> On 24 April 2012 10:17,  <dag@xxxxxxxx> wrote:
>> Hilco Wijbenga <hilco.wijbenga@xxxxxxxxx> writes:
>>
>>> 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.
>>
>> No, I think that is actually very rare.  If topic branches really should
>> be mirrored then U and S should be one repository.  They are too closely
>> coupled to be separated.  But see the but about git-subtree and topic
>> branches below.
>
> Too closely coupled? I do not think breaking up a project into a set
> of libraries makes everything tightly coupled. I would argue the
> opposite. :-) Anyway, you answer my concern below.

Indeed.  But when you make a branch in your main project, wouldn't you
usually still want to use the master branch of the libraries?  Or if
there's an experimental branch in a library and you want to use that
branched version, wouldn't you still use the master version of all the
other libraries?  What if you have two projects that both use a
library, but are otherwise unrelated?  If you create a branch called
'hotfix' in one project, do you automatically find your library
version switching to an unrelated 'hotfix' from another project?

-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]