From: "Jānis Rukšāns" <janis.ruksans@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Submodule, subtree, or something else?
Date: Sun, 23 Aug 2015 17:11:06 +0300 [thread overview]
Message-ID: <1440339066.32140.17.camel@gmail.com> (raw)
In-Reply-To: <CAGZ79kbUXwEYnpDWgKqnUab2xP4m9m7FMskaK2u8WcqnLSSoog@mail.gmail.com>
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.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?
next prev parent reply other threads:[~2015-08-23 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 22:47 Submodule, subtree, or something else? Jānis Rukšāns
2015-08-22 0:07 ` Stefan Beller
2015-08-23 14:11 ` Jānis Rukšāns [this message]
2015-08-24 16:51 ` Stefan Beller
2015-08-24 17:53 ` Jānis Rukšāns
[not found] ` <CAK6hiNiBD+DUdNq0c2DY9LWg2PCgE56SpbBip8BNNmHTsEttuQ@mail.gmail.com>
2015-08-24 17:12 ` Jānis Rukšāns
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440339066.32140.17.camel@gmail.com \
--to=janis.ruksans@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).