Nigel Magnay schrieb: > For me, in some really high proportion of cases, I think I want 'git > commit' to mean 'commit to any child repositories, any sibling > repositories, and any parent repositories (updating the submodule sha1 > as appropriate). In other words, 'pretend like the whole thing is one > big repo'. And I think that this is the problem: If this way of commiting your changes is *required* in the *majority* of cases, then you are IMO outside the intended use-case of submodules. You are better served by really making this one big repo. IMO, submodules are to be used if you can afford to advance parent project and submodules at different paces; i.e. if the parent project can work with newer versions of the submodules (and possibly in a degraded mode even with outdated versions). -- Hannes -- 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
