On Fri, Dec 06, 2013 at 02:40:15PM -0500, Martin Langhoff wrote:
> On Fri, Dec 6, 2013 at 3:48 AM, Jens Lehmann <Jens.Lehmann@xxxxxx> wrote:
> > Right you are, we need tutorials for the most prominent use cases.
>
> In the meantime, are there any hints? Emails on this list showing a
> current "smart" workflow? Blog posts? Notes on a wiki?
None that I know of mainly because we have not yet reached the goal we
are aiming at. Maybe we should write something, A few points from
$dayjob that come to my mind:
* A submodule commit is only allowed to be merged into master in a
superproject commit if it is merged into master (or a stable branch)
in the submodule. That way you ensure that any submodules commits
that are tracked in a superproject are contained in each other and
can be cleanly merged. (no rewinds, one commit contains the other)
* Submodule should be selfcontained (i.e. if its a library have tests
that use the code you implement). That way changes in the submodule
can be made independent from the superproject
* If a submodule needs another submodule have them side by side
instead of one inside another. See the next point for explanation.
* Only one depth of recursion for submodules. Even though intuition
tell you that if some submodule needs another it should contain the
other its IMO not wise to do so. There will be times when some other
submodule needs the same submodule that is contained in the other
and then you end up with two copies of the same code. My suggestion:
Let the superproject bundle all the dependencies between modules.
* Submodules are a good solution for shared code where the dependency
goes superproject needs submodule. If you divide code into
submodules because of access control and the dependency is actually
that the submodule needs the superproject it works but is less than
optimal.
Thats what I can quickly suggest and probably far from complete.
Cheers Heiko
--
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