I think (but I'm no expert here) that this is a current limitation that
is slowly being worked on upstream.
If you want to have a look at the developer list discussions try
https://public-inbox.org/git/?q=git+push+--recurse-submodules (adjust
the search to taste...)
Stephan Beller is the power behind the development. Also confirm that
you have the right settings enabled, e.g. this confusion
https://public-inbox.org/git/cagz79kabctd9uvw+gpxxjgf8bfiqvmkhka4up8gc_kxjdv-...@mail.gmail.com/
Philip
On 05/03/2019 00:19, David E wrote:
I have a case where we have a repository with nested submodules. If I
make a change in the lowest level submodule and do a push with the
recurse flag from its parent, there are no issues. However, if I jump
to the grandparent repository, it will recurse into the parent to push
(or check), but not into the lower child.
For a test, assume:
- / # Root repo, "git push recurse-submodules" will find and push
changes in parent/Level1, but does not check Level 2.
- /parent # Submodule, Level 1. "git push recurse-submodules"
works as expected at this level.
- /parent/child # Submodule, Level 2
Is this behavior that's not supported, a bug, or am I doing something
wrong here?
thanks,
-David
--
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 git-users+unsubscr...@googlegroups.com
<mailto:git-users+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
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 git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
