On Thu, 25 Sep 2014 07:54:39 -0700 (PDT) Віктор Невідомий <[email protected]> wrote:
> Very good explanation. It clarifies something. I read some comments > about using "subtree" vs "submodules". In most places people give a > bad score to "submodules". I dunno. Both are well supported, and IMO submodules is usually touted as a goto solution for cases like yours. By the way, another feature submodules have over subtree merging is that it's easier to play with different states of subprojects: say, it's easy to see how the whole project would behave if all the subprojects are in their most recent states while a single subproject is, say, in a state it was two months ago. This should be doable with subtree merging as well, but I think it will be somewhat tricky to achieve. Another perspective which might be useful to you is that if you're familiar with Subversion, submodules are like Subversion's "externals" anchored at concrete revisions. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
