How does git handle cloning another repository into a subdirectory?

Question

I just cloned a repository into a subdirectory of another repository, and git actually appeared to handle the situation pretty intelligently. I know about submodules, but I thought they always had to be explicitly defined and I didn't think git had this functionality. What happened?

Here's my shell session:

https://gist.github.com/858131

score 2 · Answer 1 · answered Mar 07 '11 at 06:17

2

The second repository is being handled as a submodule by the first repository. Since you haven't defined it as a submodule though, you can not interact with it using the git submodule command, but all other commands treat it as a submodule.

answered Mar 07 '11 at 06:17

Arrowmaster

9,143
2
28
25

OK... now that I've gotten my repository into this state, how can I tell `git submodule` to treat the second repository as a submodule? – We Are All Monica Mar 07 '11 at 06:21
@jnylen: `git submodule add git://github.com/tpope/vim-abolish.git bundle/vim-abolish` – Arrowmaster Mar 07 '11 at 06:23
That (just adding the submodule normally) only worked after I blew away what was already there. Good enough though, thanks. – We Are All Monica Mar 07 '11 at 06:32
@jnylen: I think you might've been able to get away with manually adding it to `.gitmodules`, too. – Cascabel Mar 07 '11 at 06:58

score 2 · Accepted Answer · edited May 23 '17 at 12:30

It handles it as a nested repository, not as a submodule.
As you found out, to declare it as a submodule:

the sub-directory shouldn't already exist, meaning if you already cloned your second repo, you need to delete it first before adding it as a submodule.
or you can try adding it directly in the .gitmodules file (not tested)

That will allow for the creation of the special entry in the git index referencing the submodule SHA1, as shown here, and detailed in the SO question "Nested git repositories without submodules?".

How does git handle cloning another repository into a subdirectory?

2 Answers2

Linked