Xen schreef op 23-05-2017 18:43:
But now I learn that every commit in the sub-repository must also be
met by a commit in the parent repository, which makes it a bit
annoying to do anything.
Is it possible to someone not let the parent repository care, or for
it to always point to the master branch (head) of the sub-repository?
I just notice that the behaviour for git status changed between versions
and I am using an older version (pre 2.0) on this particular server.
--ignore-submodules changed from "none" to "all".
There are probably a million issues with keeping submodules in sync and
I don't even want to know what happens when I am ignoring submodule
changes while not updating it in the parent repository?
If you don't commit those changes then git submodule update will cause
chaos if you ever choose to work in the submodule, and not just consume
it as a consumer.
--
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.
