In message <4EF26F7B.90206@xxxxxxxxx>, Neal Kreitzinger writes:
We are working on implementing this so some of what I said is
theoretical. Custom branches in combination with submodules seems like
it could get pretty unwieldy if not managed properly.
You might want to consider using gitslave (http://gitslave.sf.net)
which is easier to use when you are developing both the superproject
and the subprojects at the same time. You don't have to use the
"mother-may-I" commit protocol.
The trick with gitslave is that normally you run all git commands on
all repositories at the same time. So all repositories which are part
of the superproject will be on the same branch. This sounds like it
is ideal for you.
However, you do lose the strong binding between the superproject
commit and the subproject commit, so you would want to tag all
projects (trivial when using gitslave) when you go through a release
so that you can later go back and check out synchronized repositories
for a particular release.
-Seth Robertson
--
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