git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Git List <git@vger.kernel.org>
Subject: [RFC] Clone repositories recursive with depth 1
Date: Wed, 11 Nov 2015 15:09:18 +0100	[thread overview]
Message-ID: <DE5B8B46-B185-4258-A1C8-07E46072CD5D@gmail.com> (raw)

Hi,

I have a clean build machine and I want to clone my source code to this machine while transferring only the minimal necessary amount of data. Therefore I use this command:

git clone --recursive --depth 1 --single-branch <url>

Apparently this does not clone the submodules with "--depth 1" (using Git 2.4.9). As a workaround I tried:

git clone --depth 1 --single-branch <url>
cd <repo-name>
git submodule update --init --recursive --depth 1

However, this does not work either as I get:
fatal: reference is not a tree: <correct sha1 of the submodule referenced by the main project>
Unable to checkout <correct sha1 of the submodule referenced by the main project> in submodule path <submodule path>

How would you clone the repo? Is the behavior above expected? If not, should the "--depth 1" flag be applied recursively to all submodules on a clone --recursive? Has a patch implementing this a chance to get in?

Thanks,
Lars

             reply	other threads:[~2015-11-11 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 14:09 Lars Schneider [this message]
2015-11-11 19:19 ` [RFC] Clone repositories recursive with depth 1 Stefan Beller
2015-11-11 20:09   ` Stefan Beller
2015-11-12  9:39     ` Lars Schneider
2015-11-12 23:47       ` Stefan Beller
2015-11-14 16:25 ` Fredrik Gustafsson

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=DE5B8B46-B185-4258-A1C8-07E46072CD5D@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    /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).