On Sun, Aug 23, 2015 at 7:11 AM, Jānis Rukšāns <janis.ruks...@gmail.com> wrote: > On Pk, 2015-08-21 at 17:07 -0700, Stefan Beller wrote: >> On Fri, Aug 21, 2015 at 3:47 PM, Jānis Rukšāns <janis.ruks...@gmail.com> >> wrote: >> > >> > A major drawback of submodules in my opinion is the >> > inability to make a full clone from an existing one without having >> > access to the central repository, which is something I have to do from >> > time to time. >> >> Can you elaborate on that a bit more? >> git clone --recurse-submodules should do that no matter which remote >> you contact? > > I mean that if I have cloned a repository with submodules, cloning that > repository with --recurse-submodules will either access the "central > server" if absolute URLs are used, or requires additional clones for > each submodule. For example > > git clone --recursive http://somewhere/projectA.git > git clone --recursive file://$(pwd)/projectA projectA.tmp > > The second command will cause the submodules to be downloaded again, or > expect them to be found in $(pwd).
IIUC, the second command will lookup the submodules in $(pwd), but if they are not there they are skipped, so all of the existing submodules are cloned. Why do you need more submodules in the tmp clone than in $(pwd)/projectA would be my next question. But I see your point now. > > Or am I mistaken, or doing something wrong? > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
