From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, jacob.keller@gmail.com,
Stefan Beller <sbeller@google.com>
Subject: [PATCH 0/3] clone --shallow-submodules flag
Date: Tue, 12 Apr 2016 16:48:46 -0700 [thread overview]
Message-ID: <1460504929-19208-1-git-send-email-sbeller@google.com> (raw)
(This is a resend of a series from March 15th, titled
"Towards sane shallow clones with submodules", this series
applies on top of sb/submodule-parallel-update,
it replaces sb/clone-shallow-passthru)
When creating a shallow clone of a repository with submodules, the depth
argument does not influence the submodules, i.e. the submodules are done
as non-shallow clones. It is unclear what the best default is for the
depth of submodules of a shallow clone, so we need to have the possibility
to do all kinds of combinations:
* shallow super project with shallow submodules
e.g. build bots starting always from scratch. They want to transmit
the least amount of network data as well as using the least amount
of space on their hard drive.
* shallow super project with unshallow submodules
e.g. The superproject is just there to track a collection of repositories
and it is not important to have the relationship between the repositories
intact. However the history of the individual submodules matter.
* unshallow super project with shallow submodules
e.g. The superproject is the actual project and the submodule is a
library which is rarely touched.
The new switch to select submodules to be shallow or unshallow supports
all of these three cases.
Changes to the previous series:
* Reordered patch 1 and 2, as it sounds like a more natural ordering.
Any comments welcome!
Thanks,
Stefan
Stefan Beller (3):
clone: add `--shallow-submodules` flag
submodule clone: pass along `local` option
clone: Add t5614 to test cloning submodules with shallowness involved
Documentation/git-clone.txt | 13 +++++--
builtin/clone.c | 21 ++++++++++++
builtin/submodule--helper.c | 22 ++++++++++--
git-submodule.sh | 7 ++++
t/t5614-clone-submodules.sh | 82 +++++++++++++++++++++++++++++++++++++++++++++
5 files changed, 139 insertions(+), 6 deletions(-)
create mode 100755 t/t5614-clone-submodules.sh
--
2.5.0.264.gc776916.dirty
next reply other threads:[~2016-04-12 23:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 23:48 Stefan Beller [this message]
2016-04-12 23:48 ` [PATCH 1/3] submodule clone: pass along `local` option Stefan Beller
2016-04-25 12:18 ` Lars Schneider
2016-04-25 17:15 ` Stefan Beller
2016-04-12 23:48 ` [PATCH 2/3] clone: add `--shallow-submodules` flag Stefan Beller
2016-04-12 23:48 ` [PATCH 3/3] clone: add t5614 to test cloning submodules with shallowness involved Stefan Beller
2016-04-13 6:52 ` Jacob Keller
2016-04-25 17:41 ` Stefan Beller
2016-04-25 12:25 ` Lars Schneider
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1460504929-19208-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacob.keller@gmail.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.
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 NNTP newsgroup(s).