Reputation: 423
I am experiencing some troubles managing some repositories on Github. I am actiually mainting a pathfinding library. The master repo is here: Jumper.This repo connected to 2 others, included as submodules (30log and Binary-Heaps).
When I attempt to clone the master repo (Jumper), using --recursive as an option, it works fine.
But, when I want to include this master repo as a submodule in another one, let's call it SuperMaster repo, and then I attempt to clone SuperMaster repo, still using --recursive, it succeeds to clone the repo Jumper, but fails to register its submodules (30log and Binary-Heaps), saying something like:
Failed to recurse into submodule path
fatal: not a git repository: ../../../../c:/Users/... etc
I dug a bit, and I found some people have encountered something similar (here and here) but noone of the solutions proposed seems to work with me.
Upvotes: 4
Views: 5900
Reputation: 129526
You shouldn't have to cd
into lib/Jumper
. Call git submodule update --init --recursive
from the root of the top level repo. Submodule commands can only be executed from root of dir of a repo. Also, if you are using local urls, submodules have problems with relative paths. The error that you are getting may imply that you are using a local file path instead of a url. But most likely it's that you are not calling the submodule command from what is a root level in a repo.
Upvotes: 3