bube commented on issue #9384: URL: https://github.com/apache/paimon/issues/9384#issuecomment-5407954696
Closing as invalid — I misdiagnosed this. `.gitmodules` is not the cause. The error is generic: `git submodule <cmd>` emits it whenever it is given a pathspec with no matching tracked entry. An arbitrary path that was never a submodule produces the identical message: ``` $ git submodule update --init totally/made/up/path error: pathspec 'totally/made/up/path' did not match any file(s) known to git ``` What I verified on current master: | Condition | Result | |---|---| | `git submodule update --init --recursive` (bare) | exit 0, silent | | `git pull --recurse-submodules` across b44537dc8 | exit 0, clean `delete mode 160000` | | same + explicit `docs/themes/book` | the error | | explicit path, `.gitmodules` deleted | still errors | | explicit path, stale `.git/config` section removed | still errors | Removing `.gitmodules` does not change the behaviour in any case, so there is no bug here to fix. The trigger was a stale path reference in my local client, not in the repository. Sorry for the noise. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
