Re: Submodule, subtree, or something else?
- From
- Jānis Rukšāns <janis.ruksans@gmail.com>
- Date
- Aug 23, 2015, 14:11 UTC
- Message-ID
- <1440339066.32140.17.camel@gmail.com>
- In-Reply-To
- <CAGZ79kbUXwEYnpDWgKqnUab2xP4m9m7FMskaK2u8WcqnLSSoog@mail.gmail.com>
On Pk, 2015-08-21 at 17:07 -0700, Stefan Beller wrote:
Show 10 quoted lines
> On Fri, Aug 21, 2015 at 3:47 PM, Jānis Rukšāns <janis.ruksans@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).
Or am I mistaken, or doing something wrong?