Stefan Beller <sbel...@google.com> writes: > Consider having a submodule 'sub' and a nested submodule at 'sub/nested'. > When nested is already absorbed into sub, but sub is not absorbed into > its superproject, then we need to fixup the gitfile and core.worktree > setting for 'nested' when absorbing 'sub', but we do not need to move > its git dir around. > > Previously 'nested's gitfile contained "gitdir: ../.git/modules/nested"; > it has to be corrected to "gitdir: ../../.git/modules/sub1/modules/nested".
That sounds like a sensible way to make things consistent.
